rickyliyi
June 13, 2016, 11:36am
1
docker process works properly
docker process quited (maybe crashed),not found on the former version < 1.11.2
Docker for Mac: version: mac-v1.11.2-beta15
turn on mac
start docker for mac
working âŠ
leave to do something (locked the screen, maybe mac going to sleep)
re login in mac but the docker has been quited
1 Like
mmscott
June 13, 2016, 11:55am
2
Iâm seeing this as well⊠the menu bar app and the docker containers are all stopped.
Noticed this stack trace in the log:
Jun 12 17:37:22 lamb Docker[Exception][1220] <Error>: name:NSInternalInconsistencyException Jun 12 17:37:22 lamb Docker[Exception][1220] <Error>: reason:Failed to set posix_spawn_file_actions for fd -1 at index 0 with errno 9 Jun 12 17:37:22 lamb Docker[Exception][1220] <Error>: return adress:[140735514891482, 140735607672702, 140735515313341, 140735424780381, 4511215991, 4511230611 , 140735623244093, 140735623197707, 140735623213723, 140735623211776, 140735660279006, 140735660270401] Jun 12 17:37:22 lamb Docker[Exception][1220] <Error>: function:0 CoreFoundation 0x00007fff8a5f54f2 __exceptionPreprocess + 178 Jun 12 17:37:22 lamb Docker[Exception][1220] <Error>: function:1 libobjc.A.dylib 0x00007fff8fe70f7e objc_exception_throw + 48 Jun 12 17:37:22 lamb Docker[Exception][1220] <Error>: function:2 CoreFoundation 0x00007fff8a65c4bd +[NSException raise:format:] + 205 Jun 12 17:37:22 lamb Docker[com.docker.docker][1220] <Error>: *** 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 0x00007fff8a5f54f2 __exceptionPreprocess + 178 1 libobjc.A.dylib 0x00007fff8fe70f7e objc_exception_throw + 48 2 CoreFoundation 0x00007fff8a65c4bd +[NSException raise:format:] + 205 3 Foundation 0x00007fff8500585d -[NSConcreteTask launchWithDictionary:] + 2494 4 Docker 0x000000010ce3b177 _TTSf4gs_d___TZFC6Docker7Backend15sendRequestSyncfSST5errorGSqSS_4respSS_ + 791 5 Docker 0x000000010ce3ea93 _TFZFC6Docker7Backend27listenForDockerStateChangesFT_T_U_FT_T_ + 1459 6 libdispatch.dylib 0x00007fff90d4a93d _dispatch_call_block_and_release + 12 7 libdispatch.dylib 0x00007fff90d3f40b _dispatch_client_callout + 8 8 libdispatch.dylib 0x00007fff90d4329b _dispatch_root_queue_drain + 1890 9 libdispatch.dylib 0x00007fff90d42b00 _dispatch_worker_thread3 + 91 10 libsystem_pthread.dylib 0x00007fff9309c4de _pthread_wqthread + 1129 11 libsystem_pthread.dylib 0x00007fff9309a341 start_wqthread + 13 ) Jun 12 17:37:22 lamb Docker[Exception][1220] <Error>: function:3 Foundation 0x00007fff8500585d -[NSConcreteTask launchWithDictionary :] + 2494 Jun 12 17:37:22 lamb Docker[Exception][1220] <Error>: function:4 Docker 0x000000010ce3b177 _TTSf4gs_d___TZFC6Docker7Backend15sen dRequestSyncfSST5errorGSqSS_4respSS_ + 791 Jun 12 17:37:22 lamb Docker[Exception][1220] <Error>: function:5 Docker 0x000000010ce3ea93 _TFZFC6Docker7Backend27listenForDocke rStateChangesFT_T_U_FT_T_ + 1459 Jun 12 17:37:22 lamb Docker[Exception][1220] <Error>: function:6 libdispatch.dylib 0x00007fff90d4a93d _dispatch_call_block_and_release + 12 Jun 12 17:37:22 lamb Docker[Exception][1220] <Error>: function:7 libdispatch.dylib 0x00007fff90d3f40b _dispatch_client_callout + 8 Jun 12 17:37:22 lamb Docker[Exception][1220] <Error>: function:8 libdispatch.dylib 0x00007fff90d4329b _dispatch_root_queue_drain + 1890 Jun 12 17:37:22 lamb Docker[Exception][1220] <Error>: function:9 libdispatch.dylib 0x00007fff90d42b00 _dispatch_worker_thread3 + 91 Jun 12 17:37:22 lamb Docker[Exception][1220] <Error>: function:10 libsystem_pthread.dylib 0x00007fff9309c4de _pthread_wqthread + 1129 Jun 12 17:37:22 lamb Docker[Exception][1220] <Error>: function:11 libsystem_pthread.dylib 0x00007fff9309a341 start_wqthread + 13 Jun 12 17:37:22 lamb Docker[com.docker.docker][1220] <Error>: Signal SIGABRT caught, terminating
hulstein
June 13, 2016, 2:46pm
3
Same here, since Version 1.11.2-beta15 (build: 9168) docker just goes away after some time. It seems to be related to when the screen is locked/unlocked. Has happened twice today.
Same log error:
6/13/16 3:32:27.686 PM Docker[3798]: *** Terminating app due to uncaught exception âNSInternalInconsistencyExceptionâ, reason: âFailed to set posix_spawn_file_actions for fd -1 at index 0 with errno 9âTTSf4gs_d___TZFC6Docker7Backend15sendRequestSyncfSST5errorGSqSS_4respSS + 791TFZFC6Docker7Backend27listenForDockerStateChangesFT_T_U_FT_T + 1459
kinghuang
June 13, 2016, 4:27pm
4
I also have the same problem, new with beta15. The Docker app just disappears without a note after some time.
Installed Docker beta on an Retina 5k iMac yesterday. Freshly downloaded build. Same thing happened overnight. No container was running, but the daemon was running when I stopped working around midnight. This morning around 7am, the whale is no longer in the menubar, and âdockerâ canât communicate with its daemon, and no processes are running.
My computer does not go to sleep but the screen does lock overnight when Iâm not using it.
I see a couple of cryptic âacpid: PWRF/00000080â entry in the acpid.log but no obvious errors anywhere else. I doubt thatâs the issue.
The timestamps in $HOME/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/log seem to indicate that the crash happened right around when I unlocked the screen. (i.e. there are kern.warn messages about adjusting for NTP, and corn.info messages right up when I unlocked the screen this morning.)
It is the same for me, after the update to beta15 the docker app crashes after a while.
mmscott
June 15, 2016, 12:21pm
7
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.
criverapr
June 15, 2016, 1:08pm
8
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
==============daemon.info init: starting pid 1830, tty ââ: '/sbin/rc shutdownâ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.
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"
vnxdev
June 15, 2016, 8:21pm
11
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)
syslog shows this:
Docker[31660]: name:NSInternalInconsistencyExceptionTTSf4gs_d___TZFC6Docker7Backend15sendRequestSyncfSST5errorGSqSS_4respSS + 791TFZFC6Docker7Backend27listenForDockerStateChangesFT_T_U_FT_T + 1459TTSf4gs_d___TZFC6Docker7Backend15sendRequestSyncfSST5errorGSqSS_4respSS + 791TFZFC6Docker7Backend27listenForDockerStateChangesFT_T_U_FT_T + 1459
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/00000080daemon.info init: starting pid 4373, tty ââ: '/sbin/rc shutdownâsyslog.info syslogd exiting
arcnor
June 15, 2016, 11:44pm
13
I can also confirm it happens for me (same error) without my mac idling, just in the middle of developmentâŠ
smal
June 16, 2016, 9:04am
14
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:NSInternalInconsistencyExceptionTTSf4gs_d___TZFC6Docker7Backend15sendRequestSyncfSST5errorGSqSS_4respSS + 791TFZFC6Docker7Backend27listenForDockerStateChangesFT_T_U_FT_T + 1459TTSf4gs_d___TZFC6Docker7Backend15sendRequestSyncfSST5errorGSqSS_4respSS + 791TFZFC6Docker7Backend27listenForDockerStateChangesFT_T_U_FT_T + 1459
Other threads with same issue
Expected behavior
Docker should continue to run through the night, being available the next morning. As youâd expect from a system daemon.
Actual behavior
The latest docker daemon crashes randomly every night, and has done so since the 1.11.2-beta15 upgrade. Crash indicates file descriptor problem.
Information
System Console -> User Diagnostic Reports:
(I have multiple of these items, all being pretty much the same)
Process: Docker [29780]
Path: /Applications/âŠ
+1 I notice this nightly as wellâŠ
I am experiencing this behaviorâŠthat docker is gone from the menu bar and not running anymore each night during sleep.
Information:
It starts and functions normally when run from the applications folder the following morning.
samlet
June 17, 2016, 5:04am
16
frequently happens for me, Version 1.11.2-beta15 (build: 9168)
mattgi
June 17, 2016, 5:08am
17
Yup. me too⊠only since latest beta.
gaetan
June 17, 2016, 6:59pm
18
We are sorry about this issue.
(A few days) after updating to beta16, please come back to tell us whether you keep experiencing this crash.
2 Likes
dwamara
June 18, 2016, 2:32am
19
Is it possible to revert back to the beta14 in the meantime? It really kills the productivity.
lyleh
June 18, 2016, 6:09pm
20
Beta 16 is out, give it a try.