Supervisor has failed, shutting down: Supervisor caught an error: one of the children died

[loretoparisi]

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

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

Expected behavior

Actual behavior

Supervisor has failed, shutting down: Supervisor caught an error: one of the children died

and Diagnosis fails (it stucks)

Information

• macOS Version:
  Version 18.06.1-ce-mac73 (26764)

Diagnostic logs

Diagnostic hangs, no output - see above please.
Docker for Mac: Version 18.06.1-ce-mac73 (26764)

### Steps to reproduce the behavior
After this bug, try to generate diagnostic

[rodolfosaraiva]

+1, after energy down

[Sporky023]

@rodolfobubb

after energy down

Do you mean this happens after the computer has slept? Or after the computer's battery has been low? Or do you mean something else?

[rodolfosaraiva]

@Sporky023

Do you mean this happens after the computer has slept? Or after the computer's battery has been low? Or do you mean something else?

I'm using an Imac, this error occured when started to rain and the power was out (blackout).
Then, i turned on the computer and needed to reset docker to default (lost all mysql database).

[Sporky023]

I've added my +1 to your after energy down comment. In my case it was after my laptops battery had drained and I had to charge it to start it up again. I don't believe it did an actual boot sequence, but rather recovered from a very low battery state (somewhere between normal open-list wakeup and full system boot).

[JoeCotellese]

I'm having this same problem but it's on a desktop machine that doesn't sleep.

[hktalent]

me too,+1

Supervisor has failed, shutting down: Supervisor caught an error: one of the children died: com.docker.osxfs (pid: 23368)

Supervisor has failed, shutting down: Supervisor caught an error: one of the children died: com.docker.osxfs (pid: 10687)

[uterator]

The same issue, not a laptop. I have installed docker from scratch and can't get it working. It's just blocking me.
MacOS: 13.6

[edgarvonk]

Seems the same issue as: #3076 ?

[brampat]

+1 Fresh install using "brew cask install docker"

[freerobby]

I've hit this issue about a dozen times tonight. I'm on a laptop, but it's not low on power. I too tried doing diagnostics but it just hangs. I'm on the stable branch.

I installed Mac OS security update 2018-002 this morning and had not seen this issue prior to that update.

[kofronpi]

Same here on a fresh install of Docker CE on a macbook air - macOS mojave 10.14

[abdennour]

Same here after migrating from a MacBook pro to another MacBook. Both Macbook have the same criteria: MacBook Pro 2018, 2.6 GHz Intel Core i7, 16 GB 2400 MHz DDR4.

I migrated everything (home directory, network setting, Application) except "Other files".
I have now a doubt in the missing of "Other files" during the migration.

[roshsingh]

Same. Occurs when starting docker after the machine wakes up from sleep.

[hktalent]

#3076

[demonguru18]

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.

[Paul-Wasilewski]

I have managed to solve the problem on OS X (Version 2.0.0.0-mac81) by removing all (my customs) Paths under File Sharing. I have a strong suggestion that it might be a problem when docker.sock is shared between the containers.

[wajiii]

I frequently get this when I first start my computer for the day. I typically shut it down every night, to get a fresh start every day, and often Docker gives me errors when I first log in. I have not been keeping close track of the error messages, but I am pretty sure I have seen this one before; today, it was:

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

I try to have it run diagnostics each time, but it has only given results once or twice. I am usually in too much of a hurry to get started working to deal with it at the time, so I just tell it to reset to defaults, and move on.
Afterward, I have to recreate my containers, but we have build scripts to handle that, so it is really just a minor inconvenience...
Anyway, for any future readers:
Today, I exited the helper app after diagnostics once again failed to gather any info for me, then reinstalled as per Bram above: brew cask install docker (which required removing/renaming the existing Docker.app because Homebrew would not overwrite it).

Et voila, problem(s) solved -- for now! 👍 😨

[snoblenet]

Unfortunately, brew cask install docker did not fix it for me.

[demonguru18]

Unfortunately, brew cask install docker did not fix it for me.

Did you try this - 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.

[snoblenet]

@demonguru18 My understanding is that on Macs with that chipset, VT-X is enabled by default. But I also checked manually and it is enabled on my system.

[demonguru18]

@demonguru18 My understanding is that on Macs with that chipset, VT-X is enabled by default. But I also checked manually and it is enabled on my system.

Actually, for me I have Hackintosh - Therefore I had to set two options VT-D and VT-X both to Enabled.(I have both these options on Asus Mobo)
I am not sure if you have VT-D enabled on real mac

[luckydonald]

I now have the same issue after upgrading from 2.0.0.2 -> 2.0.0.3 via the updater.
Edit: Reboot seem to have fixed it.

[docker-robott]

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

[loretoparisi]

I confirm that this issue is still there and that rebooting will fix it.

[mkschulze]

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 solved it for me as well on a hackintosh.

[glc650]

Having this same issue on a 2018 Mac Mini with macOS 10.14.5 and Docker for Mac stable 2.0.0.3 (31259). Purchased Mini in May and setup Docker right away but didn't have this issue until about 3 weeks ago.

[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