Docker for mac auto quit

It is the same for me, after the update to beta15 the docker app crashes after a while.

For me it is always after the mac has been idle and the screen has locked. It doesn’t happen when in use. It isn’t set to sleep or anything but I’m wondering if there is something else happening a while after it is locked up for the night.

Same for me. It happens when mac is idle and goes to sleep.

Happened again in the middle of the day. Again after its been idle and the screen locked.

Saw this in $HOME/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/log/messages

==============
Jun 15 14:05:50 moby daemon.err acpid[1072]: PWRF/00000080
Jun 15 14:05:50 moby daemon.info init: starting pid 1830, tty ‘’: '/sbin/rc shutdown’
Jun 15 14:05:50 moby syslog.info syslogd exiting

So it looks like a clean shutdown initiated by the PWRF. Why does docker think someone is clicking the power button ?

Same for me.
Info: 8A30D5B0-63BE-434B-972F-788E2BBAF531

time="2016-06-15T18:54:24.819164821Z" level=info msg="Processing signal 'terminated'"
time="2016-06-15T18:54:24.819921315Z" level=debug msg="starting clean shutdown of all containers..."
time="2016-06-15T18:54:24.820712768Z" level=debug msg="Unix socket /var/lib/docker/network/files/97be455f7913dbb15692a758cea18eb4a37209ceb5345cae38f7e9487dd7221c.sock doesn't exist. cannot accept client connections"
time="2016-06-15T18:54:24.886790633Z" level=debug msg="Cleaning up old mountid : start."
time="2016-06-15T18:54:24.887962130Z" level=debug msg="Cleaning up old mountid : done."
time="2016-06-15T18:54:24.888648209Z" level=debug msg="Clean shutdown succeeded"
time="2016-06-15T18:54:24Z" level=info msg="stopping containerd after receiving terminated"
time="2016-06-15T18:54:24.889357359Z" level=debug msg="containerd connection state change: SHUTDOWN"

I can confirm that docker just exits (or crashes) in the middle or the development, no matter if mac was idle or not.

D0446D10-B124-4A5D-BF4B-4F3C3C1A8AAA

Version 1.11.2-beta15 (build: 9168)
Has exited for me several times in the last 2 or 3 days. Mac has not been idle each time but has happened with and without containers running.

syslog shows this:

Docker[31660]: name:NSInternalInconsistencyException
Docker[31660]: reason:Failed to set posix_spawn_file_actions for fd -1 at index 0 with errno 9
Docker[31660]: return adress:[140735613752538, 140735564674876, 140735614174397, 140735808755805, 4450386295, 4450400915, 140735600757053, 140735600710667, 140735600726683, 140735600724736, 140735593092318, 140735593083713]
Docker[31660]: function:0 CoreFoundation 0x00007fff9043d4f2 __exceptionPreprocess + 178
Docker[31660]: function:1 libobjc.A.dylib 0x00007fff8d56f73c objc_exception_throw + 48
Docker[31660]: function:2 CoreFoundation 0x00007fff904a44bd +[NSException raise:format:] + 205
Docker[31660]: function:3 Foundation 0x00007fff9be3585d -[NSConcreteTask launchWithDictionary:] + 2494
Docker 0x0000000109438177 TTSf4gs_d___TZFC6Docker7Backend15sendRequestSyncfSST5errorGSqSS_4respSS + 791
Docker 0x000000010943ba93 TFZFC6Docker7Backend27listenForDockerStateChangesFT_T_U_FT_T + 1459
Docker[31660]: function:6 libdispatch.dylib 0x00007fff8f7d893d _dispatch_call_block_and_release + 12
Docker[31660]: function:7 libdispatch.dylib 0x00007fff8f7cd40b _dispatch_client_callout + 8
Docker[31660]: function:8 libdispatch.dylib 0x00007fff8f7d129b _dispatch_root_queue_drain + 1890
Docker[31660]: function:9 libdispatch.dylib 0x00007fff8f7d0b00 _dispatch_worker_thread3 + 91
Docker[31660]: function:10 libsystem_pthread.dylib 0x00007fff8f0894de _pthread_wqthread + 1129
Docker[31660]: function:11 libsystem_pthread.dylib 0x00007fff8f087341 start_wqthread + 13
Docker[31660]: *** Terminating app due to uncaught exception ‘NSInternalInconsistencyException’, reason: ‘Failed to set posix_spawn_file_actions for fd -1 at index 0 with errno 9’
*** First throw call stack:
(
0 CoreFoundation 0x00007fff9043d4f2 __exceptionPreprocess + 178
1 libobjc.A.dylib 0x00007fff8d56f73c objc_exception_throw + 48
2 CoreFoundation 0x00007fff904a44bd +[NSException raise:format:] + 205
3 Foundation 0x00007fff9be3585d -[NSConcreteTask launchWithDictionary:] + 2494
Docker 0x0000000109438177 TTSf4gs_d___TZFC6Docker7Backend15sendRequestSyncfSST5errorGSqSS_4respSS + 791
Docker 0x000000010943ba93 TFZFC6Docker7Backend27listenForDockerStateChangesFT_T_U_FT_T + 1459
6 libdispatch.dylib 0x00007fff8f7d893d _dispatch_call_block_and_release + 12
7 libdispatch.dylib 0x00007fff8f7cd40b _dispatch_client_callout + 8
8 libdispatch.dylib 0x00007fff8f7d129b _dispatch_root_queue_drain + 1890
9 libdispatch.dylib 0x00007fff8f7d0b00 _dispatch_worker_thread3 + 91
10 libsystem_pthread.dylib 0x00007fff8f0894de _pthread_wqthread + 1129
11 libsystem_pthread.dylib 0x00007fff8f087341 start_wqthread + 13
)
Docker[31660]: Signal SIGABRT caught, terminating
Docker[31660]: Terminating com.docker.osx.hyperkit.linux and waiting until exit
Docker[31673]: Received SIGTERM, shutting down

I also see the following in ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/log

Jun 15 18:53:44 moby daemon.err acpid[1071 ] : PWRF/00000080
Jun 15 18:53:44 moby daemon.info init: starting pid 4373, tty ‘’: '/sbin/rc shutdown’
Jun 15 18:53:44 moby syslog.info syslogd exiting

I can also confirm it happens for me (same error) without my mac idling, just in the middle of development…

I get a very similar log in console to a above starting with NSInternalInconsistencyException. Machine was left idle from about 5pm.

15/06/2016 20:54:33.269 Docker[16631]: name:NSInternalInconsistencyException
15/06/2016 20:54:33.269 Docker[16631]: reason:Failed to set posix_spawn_file_actions for fd -1 at index 0 with errno 9
15/06/2016 20:54:33.273 Docker[16631]: return adress:[140735552992474, 140735788474238, 140735553414333, 140735770777693, 4320518519, 4320533139, 140735697406269, 140735697359883, 140735697375899, 140735697373952, 140735844361438, 140735844352833]
15/06/2016 20:54:33.274 Docker[16631]: function:0 CoreFoundation 0x00007fff8ca4b4f2 __exceptionPreprocess + 178
15/06/2016 20:54:33.274 Docker[16631]: function:1 libobjc.A.dylib 0x00007fff9aaddf7e objc_exception_throw + 48
15/06/2016 20:54:33.274 Docker[16631]: function:2 CoreFoundation 0x00007fff8cab24bd +[NSException raise:format:] + 205
15/06/2016 20:54:33.274 Docker[16631]: function:3 Foundation 0x00007fff999fd85d -[NSConcreteTask launchWithDictionary:] + 2494
15/06/2016 20:54:33.274 Docker[16631]: function:4 Docker 0x000000010185e177 TTSf4gs_d___TZFC6Docker7Backend15sendRequestSyncfSST5errorGSqSS_4respSS + 791
15/06/2016 20:54:33.274 Docker[16631]: function:5 Docker 0x0000000101861a93 TFZFC6Docker7Backend27listenForDockerStateChangesFT_T_U_FT_T + 1459
15/06/2016 20:54:33.275 Docker[16631]: function:6 libdispatch.dylib 0x00007fff9540493d _dispatch_call_block_and_release + 12
15/06/2016 20:54:33.275 Docker[16631]: function:7 libdispatch.dylib 0x00007fff953f940b _dispatch_client_callout + 8
15/06/2016 20:54:33.275 Docker[16631]: function:8 libdispatch.dylib 0x00007fff953fd29b _dispatch_root_queue_drain + 1890
15/06/2016 20:54:33.275 Docker[16631]: function:9 libdispatch.dylib 0x00007fff953fcb00 _dispatch_worker_thread3 + 91
15/06/2016 20:54:33.275 Docker[16631]: function:10 libsystem_pthread.dylib 0x00007fff9e02a4de _pthread_wqthread + 1129
15/06/2016 20:54:33.275 Docker[16631]: function:11 libsystem_pthread.dylib 0x00007fff9e028341 start_wqthread + 13
15/06/2016 20:54:33.306 Docker[16631]: Terminating com.docker.osx.hyperkit.linux and waiting until exit
15/06/2016 20:54:33.314 Docker[16644]: Received SIGTERM, shutting down
15/06/2016 20:54:33.315 Docker[16644]: Stop 1 children with order 1: com.docker.driver.amd64-linux (pid 16650)
15/06/2016 20:54:33.315 Docker[16644]: Signal terminated to com.docker.driver.amd64-linux (pid 16650)
15/06/2016 20:54:33.323 Docker[16631]: *** Terminating app due to uncaught exception ‘NSInternalInconsistencyException’, reason: ‘Failed to set posix_spawn_file_actions for fd -1 at index 0 with errno 9’
*** First throw call stack:
(
0 CoreFoundation 0x00007fff8ca4b4f2 __exceptionPreprocess + 178
1 libobjc.A.dylib 0x00007fff9aaddf7e objc_exception_throw + 48
2 CoreFoundation 0x00007fff8cab24bd +[NSException raise:format:] + 205
3 Foundation 0x00007fff999fd85d -[NSConcreteTask launchWithDictionary:] + 2494
4 Docker 0x000000010185e177 TTSf4gs_d___TZFC6Docker7Backend15sendRequestSyncfSST5errorGSqSS_4respSS + 791
5 Docker 0x0000000101861a93 TFZFC6Docker7Backend27listenForDockerStateChangesFT_T_U_FT_T + 1459
6 libdispatch.dylib 0x00007fff9540493d _dispatch_call_block_and_release + 12
7 libdispatch.dylib 0x00007fff953f940b _dispatch_client_callout + 8
8 libdispatch.dylib 0x00007fff953fd29b _dispatch_root_queue_drain + 1890
9 libdispatch.dylib 0x00007fff953fcb00 _dispatch_worker_thread3 + 91
10 libsystem_pthread.dylib 0x00007fff9e02a4de _pthread_wqthread + 1129
11 libsystem_pthread.dylib 0x00007fff9e028341 start_wqthread + 13
)
15/06/2016 20:54:33.323 Docker[16631]: Signal SIGABRT caught, terminating
15/06/2016 20:54:33.327 Docker[16650]: sending SIGTERM to com.docker.hyperkit pid 16653
15/06/2016 20:54:33.540 Docker[16644]: EOF on watchdog pipe: shutting down
15/06/2016 20:54:34.956 Docker[16650]: virtio-net-vpnkit: initialising, opts=“uuid=cd1f9730-4e9f-47d4-92ef-c4d51fe46664,path=/Users/smaloney/Library/Containers/com.docker.docker/Data/s50,macfile=/Users/smaloney/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/mac.0”
15/06/2016 20:54:34.956 Docker[16650]: Interface will have uuid cd1f9730-4e9f-47d4-92ef-c4d51fe46664
15/06/2016 20:54:34.956 Docker[16650]: Connection established with MAC=c0:ff:ee:c0:ff:ee and MTU 1500
15/06/2016 20:54:34.956 Docker[16650]: virtio-9p: initialising path=/Users/smaloney/Library/Containers/com.docker.docker/Data/s40,tag=db
15/06/2016 20:54:34.956 Docker[16650]: virtio-9p: initialising path=/Users/smaloney/Library/Containers/com.docker.docker/Data/s51,tag=port
15/06/2016 20:54:34.956 Docker[16650]: linkname /Users/smaloney/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty
15/06/2016 20:54:34.956 Docker[16650]: COM1 connected to /dev/ttys003
15/06/2016 20:54:34.956 Docker[16650]: COM1 linked to /Users/smaloney/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty
15/06/2016 20:54:34.986 Docker[16647]: Fatal unexpected exception: Transfuse.Socket_closed
15/06/2016 20:54:34.985 Docker[16648]: PPP.listen: closing connection
15/06/2016 20:54:34.994 Docker[16644]: Reap com.docker.osxfs (pid 16647): exit status 1
15/06/2016 20:54:35.003 Docker[16649]: VM has shutdown at 2016-06-15 20:54:34 +0100 IST
15/06/2016 20:54:35.008 Docker[16644]: Reap com.docker.driver.amd64-linux (pid 16650): exit status 0
15/06/2016 20:54:35.020 Docker[16644]: Stop 2 children with order 2: com.docker.osxfs (pid 16647), com.docker.slirp (pid 16648)
15/06/2016 20:54:35.020 Docker[16644]: Signal terminated to com.docker.slirp (pid 16648)
15/06/2016 20:54:35.024 Docker[16644]: Reap com.docker.slirp (pid 16648): signal: terminated
15/06/2016 20:54:35.124 Docker[16644]: Stop 1 children with order 3: com.docker.backend (pid 16649)
15/06/2016 20:54:35.124 Docker[16644]: Signal terminated to com.docker.backend (pid 16649)
15/06/2016 20:54:35.129 Docker[16644]: Reap com.docker.osx.hyperkit.linux (pid 16649): signal: terminated
15/06/2016 20:54:35.233 Docker[16644]: Stop 1 children with order 4: com.docker.db (pid 16646)
15/06/2016 20:54:35.234 Docker[16644]: Signal terminated to com.docker.db (pid 16646)
15/06/2016 20:54:35.242 Docker[16644]: Reap com.docker.db (pid 16646): exit status 1

Other threads with same issue

I am experiencing this behavior…that docker is gone from the menu bar and not running anymore each night during sleep.

Information:
Docker for Mac: version: mac-v1.11.2-beta15
OS X: version 10.11.5 (build: 15F34)
logs: /tmp/20160616-091452.tar.gz
failure: No error was detected
[OK] docker-cli
[OK] app
[OK] menubar
[OK] virtualization
[OK] system
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux

It starts and functions normally when run from the applications folder the following morning.

frequently happens for me, Version 1.11.2-beta15 (build: 9168)

Yup. me too… only since latest beta.

We are sorry about this issue.
The next beta that is coming soon, should fix it.

(A few days) after updating to beta16, please come back to tell us whether you keep experiencing this crash.

2 Likes

Is it possible to revert back to the beta14 in the meantime? It really kills the productivity.

Beta 16 is out, give it a try.

good job.
i updated beta 16 yesterday, no crash anymore until now.

I’ve had the same issue with beta 15 and beta 16. Randomly disappears from the menubar, daemon quits with no notification. I also have the very weird experience of the beta failing for often in the evening hours. Perhaps this is Docker’s way of telling me to go to bed?

Still running continuously 3 days later since upgrade to beta 16. looks good so far and thanks for addressing this bug…

1 Like

try beta 16, looks ok now

Hello there.

I’m using 1.12.0-rc2-beta17 (build: 9779) and still stoping my container when MacOS sleep.

Is there any setting to disable the container stop? Or this is a bug from this version?

Regards!

1 Like