Fatal Error: one of the sub-processes failed: com.docker.driver.amd64-linux (pid: 6160)

[caicanglun]

• I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID:

Expected behavior

Actual behavior

Information

• macOS Version:

Diagnostic logs

Docker for Mac: version...

Steps to reproduce the behavior

1. ...
2. ...

[docker-robott]

We're closing this issue because it doesn't contain enough information for us to investigate the problem.
If you'd like us to investigate further, could you please open a fresh issue with a more detailed description of the problem and a diagnostic id, following the steps at https://docs.docker.com/docker-for-mac/troubleshoot?

[maartenpaauw]

Received the same fatal error today. Just downloaded it (edge version).

[maartenpaauw]

Here is the log that I found.

com.docker.driver.amd64-linux.log

[zhuofanxu]

I just turn on the cpu virtualization on bios seting, and it works

[maartenpaauw]

I just turn on the cpu virtualization on bios seting, and it works

I have enabled virtualization in the bios and it solved the issue.

[zhuofanxu]

@maartenpaauw Yes

[yilikunNEO]

how to turn on virtualization?

[maartenpaauw]

how to turn on virtualization?

You can enable this via the BIOS. It differs per motherboard where this option can be found. It is best to google this with: "Turn virtualisation on motherboard INSERT_YOUR_MOTHERBOARD".

Edit:
I assume you're using a Hackintosh?

[SlowFamily]

If using a hackintosh- I had similar issues, which were solved by enabling virtualization in the BIOS, and removing the dart=0 startup option

[joshkremer]

If using a hackintosh- I had similar issues, which were solved by enabling virtualization in the BIOS, and removing the dart=0 startup option

I can confirm the same. I'm on a Hackintosh and after having the same issue and reading this comment, I went into my BIOS and turned off "Intel Virtualization" and that solved my issue. Thanks!

[PhilipFitzgerald]

Hi

If using a hackintosh- I had similar issues, which were solved by enabling virtualization in the BIOS, and removing the dart=0 startup option

I can confirm the same. I'm on a Hackintosh and after having the same issue and reading this comment, I went into my BIOS and turned off "Intel Virtualization" and that solved my issue. Thanks!

Hi I do not know how to access BIOS or how to turn off intel virtualization. Could you provide me with the steps? I really need to get docker working on my Mac for class quickly

[joshkremer]

Hi

If using a hackintosh- I had similar issues, which were solved by enabling virtualization in the BIOS, and removing the dart=0 startup option

I can confirm the same. I'm on a Hackintosh and after having the same issue and reading this comment, I went into my BIOS and turned off "Intel Virtualization" and that solved my issue. Thanks!

Hi I do not know how to access BIOS or how to turn off intel virtualization. Could you provide me with the steps? I really need to get docker working on my Mac for class quickly

Typically that would be achieved by restarting your machine and pressing the "Delete" button to open the BIOS, then look for something similar to "CPU virtualization" and disabling that. Good luck.

[PhilipFitzgerald]

Hi

If using a hackintosh- I had similar issues, which were solved by enabling virtualization in the BIOS, and removing the dart=0 startup option

I can confirm the same. I'm on a Hackintosh and after having the same issue and reading this comment, I went into my BIOS and turned off "Intel Virtualization" and that solved my issue. Thanks!

Hi I do not know how to access BIOS or how to turn off intel virtualization. Could you provide me with the steps? I really need to get docker working on my Mac for class quickly

Typically that would be achieved by restarting your machine and pressing the "Delete" button to open the BIOS, then look for something similar to "CPU virtualization" and disabling that. Good luck.

I just tried what you suggested and unfortunately nothing happened. I don't know if its because my macbook pro is a 2012 version or what but I cant seem to fix this issue.

[esetnik]

I am having the same error today after updating to v2.2.0.3. Docker was working fine on this system prior to the update.

[chrisbarber86]

Had the same error upgrading to v2.2.0.3. Docker was working fine before the update. Restarting docker for mac did not seem to help. Resetting docker to factory defaults however did solve this issue for me.

[PhilipFitzgerald]

Nothing I tried fixed. One day I was telling someone about it and showed them it and it was working. Worked for about a month then when I closed it (left I running the entire time because I didn’t want to risk it not working) and opened it later it wasn’t working again and hasn’t worked for weeks now. Makes no sense.

…

On Mar 19, 2020, at 7:29 PM, Chris Barber ***@***.***> wrote: Had the same error upgrading to v2.2.0.3. Docker was working fine before the update. Restarting docker for mac did not seem to help. Resetting docker to factory defaults however did solve this issue for me. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked