search

docker / for-mac

Bug reports for Docker Desktop for Mac
https://www.docker.com/products/docker#/mac
2.44k stars 118 forks source link

Fatal error: Supervisor has failed, shutting down: Supervisor caught an error: one of the children died: com.docker.driver.amd64-linux (pid: 42742) #3076

Closed natea closed 4 years ago

natea commented 6 years ago

Expected behavior

Actual behavior

Information

I saw this error message pop up: django_db_utils_operationalerror___1045___access_denied_for_user__xqueue___172_18_0_13__ _issue__34_ _regisb_openedx-docker

Diagnostic logs

Docker for Mac: version: 18.05.0-ce-mac67 (1fa4e2acfc1a52f79623add2390604515d32297e) macOS: version 10.13.5 (build: 17F77) logs: /tmp/566AF46F-1653-4F02-8C95-F1381D1814D8/20180711-065336.tar.gz failure: com.docker.driver.amd64-linux is not running [ERROR] vpnkit Unexpected error connecting to /Users/nateaune/Library/Containers/com.docker.docker/Data/s51: (Failure "Error connecting socket to 9p endpoint unix:/Users/nateaune/Library/Containers/com.docker.docker/Data/s51: Unix.Unix_error(Unix.ENOENT, \"connect\", \"\")") com.docker.vpnkit is not running [OK] virtualization hypervisor [OK] vmnetd [OK] dns [ERROR] driver.amd64-linux com.docker.driver.amd64-linux is not running [OK] virtualization VT-X [OK] app [OK] moby [OK] system [OK] moby-syslog [OK] kubernetes [OK] files [OK] env [OK] virtualization kern.hv_support [ERROR] osxfs com.docker.osxfs is not running [OK] moby-console [OK] logs [ERROR] docker-cli Connection refused (ECONNREFUSED) connecting to /var/run/docker.sock: check if service is running Connection refused (ECONNREFUSED) connecting to /Users/nateaune/Library/Containers/com.docker.docker/Data/docker.sock: check if service is running docker ps failed [OK] disk

Docker for Mac: Docker Edge 18.05.0-ce-mac67 (25042)

Steps to reproduce the behavior

  1. ...
  2. ...
kchowkchowkchow commented 5 years ago

The problem is caused because - In your Motherboards BIOS settings, you have Intel Virtualization Technology(VT-X) set as Disabled. Please set this option to Enabled and you will no longer see the Supervisor related error. Setting this to disabled, prevents VM's from using/sharing resources. Basically, stops providing hardware assistance for processors running virtualization platforms. If you have both the options VT-D and VT-X set both to Enabled. Im my Motherboard I set both to enabled. Hope this solves the problem, and you don't need to downgrade Docker.

This!!! For me this fixed it. FYI, for my Asus gryphon the bios settings was in in > Advanced > cpu confirguration.

joelash commented 5 years ago

I'm on a MacBook pro that seems to have VT-X enabled, however I still get this error and 95% of the time the computer immediately kernel panics and reboots. Any thoughts on that?

chunhei2008 commented 5 years ago

I also experienced this issue. None of the implication/suggestions seemed to work/matter:

  • Disk space
  • VT-x (N/A for Mac)
  • Reset Docker

It happens consistently for me when running front visual testing, which uses 6 concurrent headless Chrome processes in a container. (High CPU and memory utilization)

Intel VT enable ,it works!

joelash commented 5 years ago

@chunhei2008 how did you enabled Intel VT?

danielb2 commented 5 years ago

Same issue here. Docker 18.09.2, build 6247962 on MacOS Mojave. Diagnostic hangs.

danielb2 commented 5 years ago

[solved]: enabled VT-d and Intel Virtualization in UEFI

morberg commented 5 years ago

This thread seems to be a mix with people running Hackintoshes where enabling Intel VT seems to help and people running on Apple hardware where no solution is yet found.

I'm running on a Mac Mini and see this issue with docker desktop 2.0.0.3 (31259) at least once a week. Has anybody found a workaround on Apple hardware?

danielb2 commented 5 years ago

@morberg it's going to be related to the motherboard handling virtualization regardless of what you have. Any clues when booting verbose?

morberg commented 5 years ago

@morberg it's going to be related to the motherboard handling virtualization regardless of what you have. Any clues when booting verbose?

What should I do in order to boot verbose and what clues should I look for?

To clarify: I'm running on stock Apple hardware with no OS modifications.

danielb2 commented 5 years ago

@morberg the first search result: https://www.idownloadblog.com/2015/08/17/how-to-boot-your-mac-in-verbose-mode/

How about looking for anything mentioning virtualization ?

mathsigit commented 5 years ago

The problem is caused because - In your Motherboards BIOS settings, you have Intel Virtualization Technology(VT-X) set as Disabled. Please set this option to Enabled and you will no longer see the Supervisor related error. Setting this to disabled, prevents VM's from using/sharing resources. Basically, stops providing hardware assistance for processors running virtualization platforms. If you have both the options VT-D and VT-X set both to Enabled. Im my Motherboard I set both to enabled. Hope this solves the problem, and you don't need to downgrade Docker.

Enable Intel Virtualization Technology(VT-X) in BIOS works for me. Thanks a lot!

docker-robott commented 5 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale comment. Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

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

MNMelton commented 5 years ago

/remove-lifecycle stale

Startouf commented 5 years ago

I'm running into this issue as well on

Previously I was running on a version of docker that was completely fine, but after I tried to move my docker image file to a SD card a whole new mess started :

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

And I'm running docker on a genuine MacBook Pro (Retina, 13-inch, Early 2015)

zixuemeng commented 5 years ago

I'm running into this issue as well on

  • macOS 10.14.3
  • Docker version 19.03.2, build 6a30dfc

Previously I was running on a version of docker that was completely fine, but after I tried to move my docker image file to a SD card a whole new mess started :

  • My docker was working but the images were taking too much space so..
  • ...I decided to move my main docker images file to a SD card of ~60GB
  • However there was a problem because the docker Image File was actually too big, and docker did not complain before starting the transfer (while the file is sparse on my macOS FS, it is not on my SD card so the default size of 64GB for the Docker image file actually couldn't fit on my SD card. After that Docker kept crashing and I had to reset to defaults
  • On my second attempt, I first changed the image file from 64 to 32Gb, and then moved it to my SD card. It worked well.
  • Following this and a restart, my docker cannot start anymore (it kept staying in the "docker is starting mode").
  • After googling a bit I decided do uninstall docker to reinstall a fresh version. I noticed I had several brew casks left so I brew uninstall docker but despite brew reporting success messages, I still had the docker app still running, and I remembered I had installed docker from an image file, so I just removed Docker by trashing it from my app folder.
  • After reinstalling Docker from the official dmg image from Docker, my docker still won't start but now I have the following error message

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

  • Even after resetting to factory settings, the same message keeps popping up :'(

And I'm running docker on a genuine MacBook Pro (Retina, 13-inch, Early 2015)

I have encountered the same problem，is there any solution?

demonguru18 commented 5 years ago

The problem is caused because - In your Motherboards BIOS settings, you have Intel Virtualization Technology(VT-X) set as Disabled. Please set this option to Enabled and you will no longer see the Supervisor related error. Setting this to disabled, prevents VM's from using/sharing resources. Basically, stops providing hardware assistance for processors running virtualization platforms. If you have both the options VT-D and VT-X set both to Enabled. Im my Motherboard I set both to enabled. Hope this solves the problem, and you don't need to downgrade Docker.

I'm running into this issue as well on

  • macOS 10.14.3
  • Docker version 19.03.2, build 6a30dfc

Previously I was running on a version of docker that was completely fine, but after I tried to move my docker image file to a SD card a whole new mess started :

  • My docker was working but the images were taking too much space so..
  • ...I decided to move my main docker images file to a SD card of ~60GB
  • However there was a problem because the docker Image File was actually too big, and docker did not complain before starting the transfer (while the file is sparse on my macOS FS, it is not on my SD card so the default size of 64GB for the Docker image file actually couldn't fit on my SD card. After that Docker kept crashing and I had to reset to defaults
  • On my second attempt, I first changed the image file from 64 to 32Gb, and then moved it to my SD card. It worked well.
  • Following this and a restart, my docker cannot start anymore (it kept staying in the "docker is starting mode").
  • After googling a bit I decided do uninstall docker to reinstall a fresh version. I noticed I had several brew casks left so I brew uninstall docker but despite brew reporting success messages, I still had the docker app still running, and I remembered I had installed docker from an image file, so I just removed Docker by trashing it from my app folder.
  • After reinstalling Docker from the official dmg image from Docker, my docker still won't start but now I have the following error message

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

  • Even after resetting to factory settings, the same message keeps popping up :'(

And I'm running docker on a genuine MacBook Pro (Retina, 13-inch, Early 2015)

The problem is caused because - In your Motherboards BIOS settings, you have Intel Virtualization Technology(VT-X) set as Disabled. Please set this option to Enabled and you will no longer see the Supervisor related error. Setting this to disabled, prevents VM's from using/sharing resources. Basically, stops providing hardware assistance for processors running virtualization platforms. If you have both the options VT-D and VT-X set both to Enabled. Im my Motherboard I set both to enabled. Hope this solves the problem, and you don't need to downgrade Docker.

morberg commented 5 years ago

I had this exact same error for months and it had nothing to do with virtualization settings for the motherboard. (I don’t know where to change those setting for a genuine Mac. I suspect this only applies to Hackintoshes.)

My issue was caused by a bad SSD. Disk Utility found problems with my file system. Once the disk was reformatted (it couldn’t be repaired in DU) the docker issue went away.

Diamond0728 commented 5 years ago

Same problem on my macbookpro , with Catalina, I have already try many docker version. It doesnt work

Diamond0728 commented 5 years ago

Same problem on my macbookpro , with Catalina, I have already try many docker version. It doesnt work

Sometimes after my rebooting, I start docker-desktop for Mac without any application opened else. Docker runes well for few minutes, and I could pull images or run containers during it. But few minutes later, it throw this error again. Anyone else same as me?

vosscodes commented 4 years ago

same issue on a macbook pro, resolved with a full reinstall of docker from the same .dmg

docker-robott commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale comment. Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

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

docker-robott commented 4 years ago

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