https://bugzilla.redhat.com/show_bug.cgi?id=1096273
--- Comment #1 from Lukas Doktor ldoktor@redhat.com --- There is a slight difference between fedora and RHEL behavior in this situation.
[RHEL results] Actual results: [1]+ Pozastavena /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' [root@t530 eclipse_links 147]$ [debug] stdcopy.go:111 framesize: 25 Received 21, ignoring... [debug] stdcopy.go:111 framesize: 25 Received 21, ignoring...
No new lines, no output.
Output of docker daemon: [31257f3e] -job kill(d09b358f4e33b1bb1e49d7fa6e3b7c52fe618a2d36a8424b0cd4697e009f7688, TTIN) = OK (0) 2014/05/09 16:35:38 POST /v1.11/containers/d09b358f4e33b1bb1e49d7fa6e3b7c52fe618a2d36a8424b0cd4697e009f7688/kill?signal=TTIN [31257f3e] +job kill(d09b358f4e33b1bb1e49d7fa6e3b7c52fe618a2d36a8424b0cd4697e009f7688, TTIN) [31257f3e] -job kill(d09b358f4e33b1bb1e49d7fa6e3b7c52fe618a2d36a8424b0cd4697e009f7688, TTIN) = OK (0) 2014/05/09 16:35:38 http: Accept error: accept unix /var/run/docker.sock: too many open files; retrying in 5ms 2014/05/09 16:35:38 POST /v1.11/containers/d09b358f4e33b1bb1e49d7fa6e3b7c52fe618a2d36a8424b0cd4697e009f7688/kill?signal=TTIN [31257f3e] +job kill(d09b358f4e33b1bb1e49d7fa6e3b7c52fe618a2d36a8424b0cd4697e009f7688, TTIN) [31257f3e] -job kill(d09b358f4e33b1bb1e49d7fa6e3b7c52fe618a2d36a8424b0cd4697e009f7688, TTIN) = OK (0) 2014/05/09 16:35:38 http: Accept error: accept unix /var/run/docker.sock: too many open files; retrying in 10ms 2014/05/09 16:35:38 http: Accept error: accept unix /var/run/docker.sock: too many open files; retrying in 20ms 2014/05/09 16:35:38 http: Accept error: accept unix /var/run/docker.sock: too many open files; retrying in 40ms 2014/05/09 16:35:38 http: Accept error: accept unix /var/run/docker.sock: too many open files; retrying in 80ms 2014/05/09 16:35:38 http: Accept error: accept unix /var/run/docker.sock: too many open files; retrying in 160ms 2014/05/09 16:35:38 http: Accept error: accept unix /var/run/docker.sock: too many open files; retrying in 320ms 2014/05/09 16:35:39 http: Accept error: accept unix /var/run/docker.sock: too many open files; retrying in 640ms 2014/05/09 16:35:39 http: Accept error: accept unix /var/run/docker.sock: too many open files; retrying in 1s 2014/05/09 16:35:40 http: Accept error: accept unix /var/run/docker.sock: too many open files; retrying in 1s 2014/05/09 16:35:41 http: Accept error: accept unix /var/run/docker.sock: too many open files; retrying in 1s 2014/05/09 16:35:42 http: Accept error: accept unix /var/run/docker.sock: too many open files; retrying in 1s ...
docker stops printing the "Received signal..." message. I'm able to use fg to join, but the container is not responding. When I press ctrl+c in docker daemon it prints: ^C2014/05/09 16:41:26 Received signal 'interrupt', starting shutdown of docker... ^C2014/05/09 16:41:27 Received signal 'interrupt', starting shutdown of docker... 2014/05/09 16:41:27 http: Accept error: accept unix /var/run/docker.sock: too many open files; retrying in 1s ^C2014/05/09 16:41:27 Received signal 'interrupt', starting shutdown of docker...
after another ctrl+c: 2014/05/09 16:41:27 Force shutdown of docker, interrupting cleanup
and the process finishes.
When I execute the daemon again, it's unable to remove the containers: docker rm output: Error: Cannot destroy container d09b358f4e33: Driver devicemapper failed to remove root filesystem d09b358f4e33b1bb1e49d7fa6e3b7c52fe618a2d36a8424b0cd4697e009f7688: Error running removeDevice 6de66f25bd2a Error: Cannot destroy container 7a57a8a67336: Driver devicemapper failed to remove root filesystem 7a57a8a6733621bf0b043f4d121221f20853256764fd0762ec49f7f595e87ac7: Error running removeDevice 2014/05/09 16:44:29 Error: failed to remove one or more containers
Docker daemon output: 2014/05/09 16:44:07 DELETE /v1.11/containers/d09b358f4e33?force=1&v=1 [e6f019e8] +job container_delete(d09b358f4e33) Cannot destroy container d09b358f4e33: Driver devicemapper failed to remove root filesystem d09b358f4e33b1bb1e49d7fa6e3b7c52fe618a2d36a8424b0cd4697e009f7688: Error running removeDevice [e6f019e8] -job container_delete(d09b358f4e33) = ERR (1) [error] server.go:1014 Error: Cannot destroy container d09b358f4e33: Driver devicemapper failed to remove root filesystem d09b358f4e33b1bb1e49d7fa6e3b7c52fe618a2d36a8424b0cd4697e009f7688: Error running removeDevice [error] server.go:90 HTTP Error: statusCode=500 Cannot destroy container d09b358f4e33: Driver devicemapper failed to remove root filesystem d09b358f4e33b1bb1e49d7fa6e3b7c52fe618a2d36a8424b0cd4697e009f7688: Error running removeDevice 2014/05/09 16:44:17 DELETE /v1.11/containers/6de66f25bd2a?force=1&v=1 [e6f019e8] +job container_delete(6de66f25bd2a) [e6f019e8] -job container_delete(6de66f25bd2a) = OK (0) 2014/05/09 16:44:18 DELETE /v1.11/containers/7a57a8a67336?force=1&v=1 [e6f019e8] +job container_delete(7a57a8a67336) Cannot destroy container 7a57a8a67336: Driver devicemapper failed to remove root filesystem 7a57a8a6733621bf0b043f4d121221f20853256764fd0762ec49f7f595e87ac7: Error running removeDevice [e6f019e8] -job container_delete(7a57a8a67336) = ERR (1) [error] server.go:1014 Error: Cannot destroy container 7a57a8a67336: Driver devicemapper failed to remove root filesystem 7a57a8a6733621bf0b043f4d121221f20853256764fd0762ec49f7f595e87ac7: Error running removeDevice [error] server.go:90 HTTP Error: statusCode=500 Cannot destroy container 7a57a8a67336: Driver devicemapper failed to remove root filesystem 7a57a8a6733621bf0b043f4d121221f20853256764fd0762ec49f7f595e87ac7: Error running removeDevice
mount output: ... /dev/mapper/docker-253:3-4065163-7a57a8a6733621bf0b043f4d121221f20853256764fd0762ec49f7f595e87ac7 on /home/medic/Work/Projekty/Docker/root/devicemapper/mnt/7a57a8a6733621bf0b043f4d121221f20853256764fd0762ec49f7f595e87ac7 type ext4 (rw,relatime,seclabel,discard,stripe=16,data=ordered) /dev/mapper/docker-253:3-4065163-d09b358f4e33b1bb1e49d7fa6e3b7c52fe618a2d36a8424b0cd4697e009f7688 on /home/medic/Work/Projekty/Docker/root/devicemapper/mnt/d09b358f4e33b1bb1e49d7fa6e3b7c52fe618a2d36a8424b0cd4697e009f7688 type ext4 (rw,relatime,seclabel,discard,stripe=16,data=ordered)
docker ps -a output: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
When I try to create the container again it fails with: [root@t530 eclipse_links 2]$ /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' [debug] hijack.go:96 [hijack] End of stdout [debug] commands.go:1958 End of CmdRun(), Waiting for hijack to finish. 2014/05/09 16:46:06 Error: Cannot start container 399677e64c6b8414d39bf316b99f667cb26c76b2d87266124998726acda391d5: Cannot find child for /test_eoly
Docker daemon output: 2014/05/09 16:46:06 POST /v1.11/containers/create?name=test_eoly [e6f019e8] +job create(test_eoly) -----> setting mount label discard [e6f019e8] -job create(test_eoly) = OK (0) 2014/05/09 16:46:06 POST /v1.11/containers/399677e64c6b8414d39bf316b99f667cb26c76b2d87266124998726acda391d5/attach?stderr=1&stdin=1&stdout=1&stream=1 [e6f019e8] +job inspect(399677e64c6b8414d39bf316b99f667cb26c76b2d87266124998726acda391d5, container) [e6f019e8] -job inspect(399677e64c6b8414d39bf316b99f667cb26c76b2d87266124998726acda391d5, container) = OK (0) [e6f019e8] +job attach(399677e64c6b8414d39bf316b99f667cb26c76b2d87266124998726acda391d5) 2014/05/09 16:46:06 POST /v1.11/containers/399677e64c6b8414d39bf316b99f667cb26c76b2d87266124998726acda391d5/start [e6f019e8] +job start(399677e64c6b8414d39bf316b99f667cb26c76b2d87266124998726acda391d5) -----> setting mount label discard [e6f019e8] +job allocate_interface(399677e64c6b8414d39bf316b99f667cb26c76b2d87266124998726acda391d5) [e6f019e8] -job allocate_interface(399677e64c6b8414d39bf316b99f667cb26c76b2d87266124998726acda391d5) = OK (0) [e6f019e8] +job release_interface(399677e64c6b8414d39bf316b99f667cb26c76b2d87266124998726acda391d5) [e6f019e8] -job release_interface(399677e64c6b8414d39bf316b99f667cb26c76b2d87266124998726acda391d5) = OK (0) [e6f019e8] -job attach(399677e64c6b8414d39bf316b99f667cb26c76b2d87266124998726acda391d5) = OK (0) Cannot start container 399677e64c6b8414d39bf316b99f667cb26c76b2d87266124998726acda391d5: Cannot find child for /test_eoly [e6f019e8] -job start(399677e64c6b8414d39bf316b99f667cb26c76b2d87266124998726acda391d5) = ERR (1) [error] server.go:1014 Error: Cannot start container 399677e64c6b8414d39bf316b99f667cb26c76b2d87266124998726acda391d5: Cannot find child for /test_eoly [error] server.go:90 HTTP Error: statusCode=500 Cannot start container 399677e64c6b8414d39bf316b99f667cb26c76b2d87266124998726acda391d5: Cannot find child for /test_eoly
When I repeat the exact same command once again (without restarting the daemon) it passes: 2014/05/09 16:48:33 POST /v1.11/containers/create?name=test_eoly [e6f019e8] +job create(test_eoly) -----> setting mount label discard [e6f019e8] -job create(test_eoly) = OK (0) 2014/05/09 16:48:33 POST /v1.11/containers/4aff2c82307724735a2a1c3b8723022b01642142836f9fd57c244f494eb5e234/attach?stderr=1&stdin=1&stdout=1&stream=1 [e6f019e8] +job inspect(4aff2c82307724735a2a1c3b8723022b01642142836f9fd57c244f494eb5e234, container) [e6f019e8] -job inspect(4aff2c82307724735a2a1c3b8723022b01642142836f9fd57c244f494eb5e234, container) = OK (0) [e6f019e8] +job attach(4aff2c82307724735a2a1c3b8723022b01642142836f9fd57c244f494eb5e234) 2014/05/09 16:48:33 POST /v1.11/containers/4aff2c82307724735a2a1c3b8723022b01642142836f9fd57c244f494eb5e234/start [e6f019e8] +job start(4aff2c82307724735a2a1c3b8723022b01642142836f9fd57c244f494eb5e234) -----> setting mount label discard [e6f019e8] +job allocate_interface(4aff2c82307724735a2a1c3b8723022b01642142836f9fd57c244f494eb5e234) [e6f019e8] -job allocate_interface(4aff2c82307724735a2a1c3b8723022b01642142836f9fd57c244f494eb5e234) = OK (0) [e6f019e8] -job start(4aff2c82307724735a2a1c3b8723022b01642142836f9fd57c244f494eb5e234) = OK (0)