Running containers die when machine suspended

[stewart123579]

Expected behavior

When I suspend my machine, running containers continue at wake.

Actual behavior

When I suspend my machine, any running containers die with the error:

Error response from daemon: dial unix /Users/ME/Library/Containers/com.docker.docker/Data/*00000003.00000948: connect: connection refused

This is an issue that I raised 3 months ago... 12-May:
https://forums.docker.com/t/running-containers-die-when-machine-suspended/11976

Information

Diagnostic ID: 87389479-4F8F-4632-8BE8-591E5125A816
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.10.5 (Build 14F1909)
[OK] docker-cli
[OK] app
[OK] moby-syslog
[OK] disk
[OK] virtualization
[OK] system
[OK] menubar
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. Start a container
2. Close lid of laptop to suspend
3. Open lid and log in
4. Get annoyed that your containers are all dead and you have to restart them...

[sleep1661]

when will fix this?

[robshox]

Experiencing this problem on Macbook pro yosemite 10.10.5 when Mac goes to sleep. Super frustrating to start containers all over again. Anyone have a fix or workaround?

[kodeninja]

+1

I have the same issue on my MacBook Pro (Retina, 15-inch, Mid 2015)/ OS X Yosemite 10.10.5.

Sometimes, I can just click on restart from the Docker icon from the dock, and it starts working properly. But mostly, I have to Quit it and relaunch docker.

Docker for Mac: version: mac-v1.12.0-beta21.1
OS X: version 10.10.5 (build: 14F1605)
logs: /tmp/E0CDD283-3799-4AC1-8200-473F5EDAF115/20160804-114325.tar.gz
[OK]     docker-cli
[OK]     app
[OK]     moby-syslog
[OK]     disk
[OK]     virtualization
[OK]     system
[OK]     menubar
[OK]     osxfs
[OK]     db
[OK]     slirp
[OK]     moby-console
[OK]     logs
[OK]     vmnetd
[OK]     env
[OK]     moby
[OK]     driver.amd64-linux

[stewart123579]

Re a fix: Don't use native Docker.

docker-machine works perfectly through sleep-wake cycles.

The only think that seems to cause it problems is when my machine runs low on power (~5%) and something (OSX?) causes it to die/kills it.

[dave-tucker]

For those who are experiencing this issue, please could you post the output of sudo pmset -g in addition to your Diagnose output. It would also be good to know if you have manually "tweaked" any of your Mac's power management settings (e.g I have mine set to disable hibernation). Using the latest version, I'm unable to replicate. I have an nginx container that's been running in the background for the last 3 hours while I've opened and closed my laptop lid on at least 10 occasions.

[amilstead]

👍 I have this issue as well, containers that were up when I close my lid are dead when I open it and log back in.

@v4tech I'm not positive that "Don't use native Docker" is really a great solution here...

On simple suspend/awake after a short period of time I don't need to restart but if it's been a while or I switch networks (e.g. VPN previously connected when lid was open and dies on lid close) I'll have to Quit the app and reload.

Diagnostic Info:

Docker for Mac: version: win-beta-v1.12.0-rc5-beta21-73-g9cd1dc2
OS X: version 10.10.5 (build: 14F27)
logs: /tmp/F0FF0465-B609-4ED4-B336-20A2F37B3F63/20160805-104933.tar.gz
[OK]     docker-cli
[OK]     app
[OK]     moby-syslog
[OK]     disk
[OK]     virtualization
[OK]     system
[OK]     menubar
[OK]     osxfs
[OK]     db
[OK]     slirp
[OK]     moby-console
[OK]     logs
[OK]     vmnetd
[OK]     env
[OK]     moby
[OK]     driver.amd64-linux

For sudo pmset -g:

$ sudo pmset -g
Active Profiles:
Battery Power        -1*
AC Power        -1
Currently in use:
 standbydelay         10800
 standby              1
 halfdim              1
 hibernatefile        /var/vm/sleepimage
 darkwakes            0
 gpuswitch            2
 disksleep            10
 sleep                0
 autopoweroffdelay    14400
 hibernatemode        3
 autopoweroff         1
 ttyskeepawake        1
 displaysleep         30
 acwake               0
 lidwake              1

[dave-tucker]

Thanks @amilstead

On simple suspend/awake after a short period of time I don't need to restart but if it's been a while or I switch networks (e.g. VPN previously connected when lid was open and dies on lid close)

This is really helpful. I have a theory about why this could be happening... It's possible this is related to OSX's "Safe Sleep" mode, which by the config above would happen 3hrs after your machine has been put in to Sleep.

For others responding to this, please could you let us know "how long" it's been after closing the lid that you notice this issue - hopefully we'll start seeing some correlation between that and the standbydelay

And if you know anyone who, like me has done a sudo pmset -a hibernatemode 0, it would be good to confirm if they see this issue at all.

As for the changing networks, this is know issue - I'm working on pushing a notification after a network change is detected to ask you if you want to restart.

[amilstead]

Awesome -- glad I could help! Should I try running sudo pmset -a hibernatemode 0 and see if that prevents this going forward, or keep it non-zero for now?

[dave-tucker]

@amilstead that's up to you...
From the manpage:

 hibernatemode = 0 (binary 0000) by default on supported desktops. The system will not back memory up to
     persistent storage. The system must wake from the contents of memory; the system will lose context on
     power loss. This is, historically, plain old sleep.

I wouldn't recommend this as a fix to anyone unless you fully understand and are happy with the consequences 😀

[amilstead]

Got it -- thanks!

[Taik]

I'm also having this problem. Notably, I'm running under a modified hibernate mode (25) for better battery life.

Diagnostic info:

Docker for Mac: version: mac-v1.12.0-beta21.1
OS X: version 10.11.6 (build: 15G31)
logs: /tmp/7C7664CF-B5E6-4AF2-8FD9-86FDDAD97A11/20160805-144645.tar.gz
[OK]     docker-cli
[OK]     app
[OK]     moby-syslog
[OK]     disk
[OK]     virtualization
[OK]     system
[OK]     menubar
[OK]     osxfs
[OK]     db
[OK]     slirp
[OK]     moby-console
[OK]     logs
[OK]     vmnetd
[OK]     env
[OK]     moby
[OK]     driver.amd64-linux

pmset:

$ sudo pmset -g
Password:
Active Profiles:
Battery Power       -1
AC Power        -1*
Currently in use:
 standbydelay         10800
 standby              1
 womp                 1
 halfdim              1
 hibernatefile        /var/vm/sleepimage
 powernap             1
 networkoversleep     0
 disksleep            0
 sleep                0
 autopoweroffdelay    14400
 hibernatemode        25
 autopoweroff         1
 ttyskeepawake        1
 displaysleep         30
 acwake               0
 lidwake              0

[sambernard]

Deleted my previous comment and reposting with pmset data.

I'm experiencing this as well, multiple times per hour after the lastest update.

I do not have to suspend my computer for it to occur.

Diagnostic ID: ABC53D7A-8C28-42F0-BB36-0CF429E11C37
Docker for Mac: 1.12.0-beta21 (Build 11019)
macOS: Version 10.11.5 (Build 15F34)
[OK]     docker-cli
[OK]     app
[OK]     moby-syslog
[OK]     disk
[OK]     virtualization
[OK]     system
[OK]     menubar
[OK]     osxfs
[OK]     db
[OK]     slirp
[OK]     moby-console
[OK]     logs
[OK]     vmnetd
[OK]     env
[OK]     moby
[OK]     driver.amd64-linux

pmset output:

Active Profiles:
Battery Power       -1
AC Power        -1*
Currently in use:
 standbydelay         10800
 standby              1
 womp                 1
 halfdim              1
 hibernatefile        /var/vm/sleepimage
 powernap             1
 gpuswitch            2
 networkoversleep     0
 disksleep            0
 sleep                0 (sleep prevented by coreaudiod)
 autopoweroffdelay    14400
 hibernatemode        3
 autopoweroff         1
 ttyskeepawake        1
 displaysleep         10
 acwake               0
 lidwake              1

[pgraci]

Same situation as @sambernard this is happening multiple times a day while I am using Docker after latest update.

Diagnostic ID: 19447443-5A44-4FB7-81E7-D19A4835A7E4
Docker for Mac: 1.12.0-beta21 (Build 11019)
macOS: Version 10.11.3 (Build 15D21)
[OK]     docker-cli
[OK]     app
[OK]     moby-syslog
[OK]     disk
[OK]     virtualization
[OK]     system
[OK]     menubar
[OK]     osxfs
[OK]     db
[OK]     slirp
[OK]     moby-console
[OK]     logs
[OK]     vmnetd
[OK]     env
[OK]     moby
[OK]     driver.amd64-linux

pmset

Active Profiles:
Battery Power       -1
AC Power        2*
Currently in use:
 standbydelay         10800
 standby              1
 womp                 1
 halfdim              1
 hibernatefile        /var/vm/sleepimage
 gpuswitch            2
 powernap             1
 networkoversleep     0
 disksleep            10
 sleep                1 (sleep prevented by coreaudiod, Google Chrome)
 autopoweroffdelay    14400
 hibernatemode        3
 autopoweroff         1
 ttyskeepawake        1
 displaysleep         10
 acwake               0
 lidwake              1

[stewart123579]

@dave-tucker :
I don't know if this helps, but there seems to be a minimum amount of time the machine needs to be suspended... A short suspend-wake doesn't seem to always trigger this bug. Similar to your point.

It is definitely not three hours or anything similar... A much shorter time.

Hi @amilstead, thanks, for your comments:

Re: sudo pmset -g

Active Profiles:
Battery Power           1
AC Power                -1*
Currently in use:
 standbydelay         10800
 standby              1
 womp                 1
 halfdim              1
 hibernatefile        /var/vm/sleepimage
 darkwakes            0
 gpuswitch            2
 networkoversleep     0
 disksleep            10
 sleep                10
 autopoweroffdelay    14400
 hibernatemode        3
 autopoweroff         1
 ttyskeepawake        1
 displaysleep         10
 acwake               0
 lidwake              1

Re: my 'don't use it' - there's two things to be taken from that:

1. If you need to have docker running (for work say) then a work around solution is required...
2. I think it's actually quite helpful, knowing that one virtualisation solution (virtualbox in my case) works but the native one doesn't. It should be somewhat useful for debugging...

[gumho]

I'm seeing this issue on my Mac with the latest Docker for Mac as well. Happens when I close my laptop lid for even a few minutes.

As @v4tech mentioned, VirtualBox can survive multiple sleeps with no issues so odd that Docker does not do this.

[jeff-xoom]

I see the same issue only after a few seconds of sleep.

Docker for Mac: version: mac-v1.12.0.1
OS X: version 10.10.5 (build: 14F1909)
logs: /tmp/264231A3-7008-4FAA-9D89-83D089716817/20160817-135639.tar.gz
[OK]     docker-cli
[OK]     app
[OK]     moby-syslog
[OK]     disk
[OK]     virtualization
[OK]     system
[OK]     menubar
[OK]     osxfs
[OK]     db
[OK]     slirp
[OK]     moby-console
[OK]     logs
[OK]     vmnetd
[OK]     env
[OK]     moby
[OK]     driver.amd64-linux

pmset

System-wide power settings:
 DestroyFVKeyOnStandby      0
Active Profiles:
Battery Power       -1
AC Power        2*
Currently in use:
 standbydelay         4200
 standby              1
 womp                 1
 halfdim              1
 hibernatefile        /var/vm/sleepimage
 gpuswitch            2
 darkwakes            1
 networkoversleep     0
 disksleep            10
 sleep                10
 autopoweroffdelay    14400
 hibernatemode        3
 autopoweroff         1
 ttyskeepawake        1
 displaysleep         10
 acwake               0
 lidwake              1

[esfoobar]

I am seeing this all the time after the update, no suspend necessary. I've closed and restarted Docker client for Mac without any luck:

Exception in thread Thread-4:
Traceback (most recent call last):
  File "threading.py", line 810, in __bootstrap_inner
  File "threading.py", line 763, in run
  File "compose/cli/log_printer.py", line 149, in tail_container_logs
  File "compose/cli/log_printer.py", line 179, in wait_on_exit
  File "compose/container.py", line 239, in wait
  File "site-packages/docker/utils/decorators.py", line 21, in wrapped
  File "site-packages/docker/api/container.py", line 441, in wait
  File "site-packages/docker/client.py", line 174, in _raise_for_status
APIError: 500 Server Error: Internal Server Error ("dial unix /Users/jorge/Library/Containers/com.docker.docker/Data/*00000003.00000948: connect: connection refused")

Exception in thread Thread-3:
Traceback (most recent call last):
  File "threading.py", line 810, in __bootstrap_inner
  File "threading.py", line 763, in run
  File "compose/cli/log_printer.py", line 149, in tail_container_logs
  File "compose/cli/log_printer.py", line 179, in wait_on_exit
  File "compose/container.py", line 239, in wait
  File "site-packages/docker/utils/decorators.py", line 21, in wrapped
  File "site-packages/docker/api/container.py", line 441, in wait
  File "site-packages/docker/client.py", line 174, in _raise_for_status
APIError: 500 Server Error: Internal Server Error ("dial unix /Users/jorge/Library/Containers/com.docker.docker/Data/*00000003.00000948: connect: connection refused")

Docker for Mac: version: mac-v1.12.0.1
OS X: version 10.11.6 (build: 15G31)
logs: /tmp/E2939754-ABEA-44FF-A4C6-91B61C3E3F68/20160824-172950.tar.gz
[OK]     docker-cli
[OK]     app
[OK]     moby-syslog
[OK]     disk
[OK]     virtualization
[OK]     system
[OK]     menubar
[OK]     osxfs
[OK]     db
[OK]     slirp
[OK]     moby-console
[OK]     logs
[OK]     vmnetd
[OK]     env
[OK]     moby
[OK]     driver.amd64-linux

sudo pmset -g
Battery Power       -1
AC Power            -1*
Currently in use:
 standbydelay         10800
 standby              1
 womp                 1
 halfdim              1
 hibernatefile        /var/vm/sleepimage
 gpuswitch            2
 powernap             1
 networkoversleep     0
 disksleep            10
 sleep                1 (sleep prevented by Google Chrome, coreaudiod)
 autopoweroffdelay    14400
 hibernatemode        3
 autopoweroff         1
 ttyskeepawake        1
 displaysleep         10
 acwake               0
 lidwake              1

[jamesdixon]

Is there any update on this issue? This is a real killer.

[dsheets]

We have not been able to reproduce this issue, unfortunately. Any and all information about your specific environment would be helpful. We are working on adding more diagnostic information regarding power events that may help us track down the cause in a future release.

[jamesdixon]

We have not been able to reproduce this issue

That is a true bummer 😢

Here's my diagnostic output:

Docker for Mac: version: 1.12.1-beta24 (0afa5e5)
OS X: version 10.10.5 (build: 14F1909)
logs: /tmp/9ED5A2D8-F249-4F5C-84F3-EB0EB3640807/20160901-124227.tar.gz
[OK]     docker-cli
[OK]     virtualization kern.hv_support
[OK]     menubar
[OK]     moby-syslog
[OK]     dns
[OK]     disk
[OK]     system
[OK]     app
[OK]     osxfs
[OK]     virtualization VT-X
[OK]     db
[OK]     slirp
[OK]     logs
[OK]     env
[OK]     vmnetd
[OK]     moby-console
[OK]     moby
[OK]     driver.amd64-linux

And power settings:

Active Profiles:
Battery Power       -1
AC Power            -1*
Currently in use:
 standbydelay         10800
 standby              1
 womp                 1
 halfdim              1
 hibernatefile        /var/vm/sleepimage
 darkwakes            1
 networkoversleep     0
 disksleep            10
 sleep                1
 autopoweroffdelay    14400
 hibernatemode        3
 autopoweroff         1
 ttyskeepawake        1
 displaysleep         10
 acwake               0
 lidwake              1

[jamesdixon]

Also, I tried setting hibernatemode to 0 with no luck; the issue still persisted.

In terms of time before I see the issue occur, it's hard to say, but I can say that I've seen it happen in as little as 15 - 20 minutes after my machine sleeps.

[stewart123579]

@dsheets - What info would you like?

I agree with @jamesdixon that this is a bummer, but as there are just soooo many of us with this problem we surely can get enough info for you.

Going out on a limb with additional info:

I don't know if this will be of assistance, but I've got a whole lot of homebrew packages installed - including coreutils replacing the mac defaults.

Does anyone/everyone else use homebrew? More importantly, does anyone have a base install to test on?

[gumho]

@v4tech I and all my colleagues who are experiencing the same problem are also using HomeBrew too

[jamesdixon]

I also have homebrew installed, but not heavily used whatsoever.

Looking at everyone's responses, I was curious if this has something to do specifically with the Hypervisor implementation in Yosemite, but it also appears there were a couple who were using El Capitain.

[ijc]

@v4tech yes, we believe this issue is fixed on 10.12 and 10.11.6 now that we have disabled the ACPI crash workaround by default on those versions. If you are upgrading from an older docker for mac then you will need to either follow the steps in #85 (comment) or perform a factory reset to pickup the new default.

[c0bra]

@v4tech @ijc25 I just tried the fix and it worked for me. My containers were not killed while my laptop was closed overnight.

[c0bra]

Reversion after latest update :(

Hard-linking to fix so I can find it again without trying: #85 (comment)

[jscheel]

I am experiencing this issue while using docker-machine. Is there any connection between the two?

[dobegor]

I have this issue running Docker for Mac Edge on OS X 10.12.5.
@ijc25 reopen?

[chrisamiller]

I also have this issue with Docker Community Edition v 17.03.1-ce-mac12 (17661) - channel stable. I've also tried pausing the docker image first, but still get a crash while it's paused: (ERRO[0388] error getting events from daemon: EOF)

[Ralle]

Running a Hackintosh on Sierra. My Docker seems to restart after sleep/wake.

Running "Docker 17.06.0-ce-mac18"

[ghost]

This is happening to me too:

Version 17.06.0-ce-mac18 (18433)
Channel: stable
d9b66511e0

[dobegor]

@ijc this needs to be reopened. I was able to reproduce it on 3 machines. Docker restarts every time machine goes to sleep.

[djs55]

@dobegor could you upload diagnostics? Alternatively have a look in your logs for a line like this

<Warning>: Triggering a VM reboot because proxy settings changed from 
main.proxySettings{http:"", https:"", exclude:""} to main.proxySettings{http:"", https:"", exclude:"*.local, 169.254/16"}

If this line is present then the issue is the same as #1809, a fix for which is scheduled for 17.06.1 hopefully this week. In the meantime a workaround is to disable HTTP proxy tracking by: Whale menu -> Preferences... -> Proxies -> No Proxy.

[dobegor]

@djs55 where can I find logs? Diagnostics menu is just hanging for a long time.

[dobegor]

@djs55 found it. yes, it was the proxy change. I wonder why the hell it happens when I unplug the charging cable, though. Maybe OS X is doing some things with rearranging type-c connected devices (including type c ethernet bridge I have on the other port).

[dobegor]

Diagnostic ID: 91ABEF61-928F-40F8-AC04-799015DC401B
Docker for Mac: version: 17.06.0-ce-mac17 (4cdec4294a50b2233146b09469b49937dabdebdd)
macOS: version 10.12.5 (build: 16F73)
logs: /tmp/91ABEF61-928F-40F8-AC04-799015DC401B/20170706-112848.tar.gz
[OK]     db.git
[OK]     vmnetd
[OK]     dns
[OK]     driver.amd64-linux
[OK]     virtualization VT-X
[OK]     app
[OK]     moby
[OK]     system
[OK]     moby-syslog
[OK]     db
[OK]     env
[OK]     virtualization kern.hv_support
[OK]     slirp
[OK]     osxfs
[OK]     moby-console
[OK]     logs
[OK]     docker-cli
[OK]     menubar
[OK]     disk

[djs55]

@dobegor thanks for the diagnostics. It does look the same as #1809 to me.

[daveisfera]

Mine froze up last night: 91BA0B97-2185-40E4-8CF7-F4C94774E732

[asoltesz]

My containers still die immediately after suspend/resume.

Docker Version: Version 17.06.0-ce-mac18 (18433)
OSX Version: 10.11.3 El Capitan

It seems that containers even die when you change settings in Energy Management of OSX (when you try to make your Mac always-on).

This is a HUGE problem, renders Docker for Mac very-very hard to use.

[ghost]

I'm now running 17.06.0-ce-mac17 (18432) and after changing the settings to "No proxy" I haven't had any problems.

[pirminis]

@DarkerMatter this solution worked for me too.

[jedihe]

The fix posted by @djs55 works for me (tested with manually triggering Sleep and also by closing the lid). Both 'No proxy' / 'Use system proxy' work fine. Longest time I kept the lid closed was ~30 min.

I'm running:

• OS X Yosemite (10.10.5)
• Docker version 17.06.0-ce, build 02c1d87

Fix with minor adjustment:

cd ~/Library/Containers/com.docker.docker/Data/database
git reset --hard
echo "please do not freeze" > com.docker.driver.amd64-linux/on-sleep
git add com.docker.driver.amd64-linux/on-sleep
git commit -m "disable freeze workaround"

[stewart123579]

Sadly the recurrence of both this issue and #1175 means that I've stayed with v1.13.0! ☹️

It seems stable and hasn't caused me any problems.

[gitfoxi]

Hi. I'm a new Docker user. This is all a bit confusing. But me too!

Version 17.06.1-ce-mac24 (18950)
Channel: stable
54dc09c3e3

I am running the High Sierra beta:

10.13 Beta (17A360a)

sudo pmset -g
Enter PIN for 'Certificate For PIV Authentication (Yubico PIV Authentication)':
System-wide power settings:
Currently in use:
 standbydelay         10800
 standby              1
 halfdim              1
 hibernatefile        /var/vm/sleepimage
 powernap             1
 gpuswitch            2
 disksleep            10
 sleep                0
 autopoweroffdelay    0
 hibernatemode        3
 autopoweroff         0
 ttyskeepawake        1
 displaysleep         0
 acwake               0
 lidwake              1

I haven't tried any of the above workaround disablers yet. Seems like black magic. But that's my next step.

[lambdaq]

Same problem on Yosemite

Version 17.12.0-ce-mac55 (23011)

Active Profiles:
Battery Power  		-1*
AC Power       		-1
Currently in use:
 standbydelay         10800
 standby              1
 halfdim              1
 hibernatefile        /var/vm/sleepimage
 darkwakes            0
 disksleep            10
 sleep                1
 autopoweroffdelay    14400
 hibernatemode        0
 autopoweroff         1
 ttyskeepawake        1
 displaysleep         2
 acwake               0
 lidwake              1

[esseti]

I still have the same problem, running Mojave, version Version 2.0.0.0-mac81 (29211)

everytime when mac wake up the docker shows the screen that allows you to reset it (but deletes everything) or exit. that's super annoying.

Any help?

PS: there's no no proxy parameter in config. any idea what could be?

looking into the logs, don't know if it can be of any help

[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