Having problem with Docker Overlay Storage Driver

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Windows
  • Memory / Disk: 32GB
  • Deployment: On Docker with both Hyper-V and also WSL2 (tried both typed but the problem is same)
  • Airbyte Version: 0.40.32
  • Description: My airbyte-db container often got shut-down and then when I try to start it again, it shows that docker cannot start the container because of overlay invalid argument

I have been searching solution for a while, they recommend to change the storage driver from overlay to device-mapper, or remove all data in docker and restart again

The first solution doesn’t work for Docker Windowns,

The second one is very annoying when this issue occurs 2 days in a row for me, so I have to manually remove/ re-install Docker again and again

Is there any way to fix this with?

Below is my Docker Info

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team