Created attachment 911745[details]
/var/log/messages output
Description of problem:
Sometimes when I try to start container I get this message:
2014/06/24 13:39:34 finalize namespace drop bounding set read /proc/1/status: bad file descriptor
and the container is not started.
Version-Release number of selected component (if applicable):
docker-io-1.0.0-1.fc20.x86_64
How reproducible:
rarely
Steps to Reproduce:
1. use `docker run ...` (in this example: `/usr/bin/docker -D run --interactive --tty --name test_eHmi localhost:5000/ldoktor/fedora:latest bash -c bash`
Actual results:
Container is not started, message:
2014/06/24 13:39:34 finalize namespace drop bounding set read /proc/1/status: bad file descriptor
is in the container output.
Expected results:
Container should start.
Additional info:
There were around 14 containers running and 2 not running when this bug occurred. This bug happened to me 3 or 4 times during one week (testing docker, so the failure percentage is really low).
Created attachment 911745 [details] /var/log/messages output Description of problem: Sometimes when I try to start container I get this message: 2014/06/24 13:39:34 finalize namespace drop bounding set read /proc/1/status: bad file descriptor and the container is not started. Version-Release number of selected component (if applicable): docker-io-1.0.0-1.fc20.x86_64 How reproducible: rarely Steps to Reproduce: 1. use `docker run ...` (in this example: `/usr/bin/docker -D run --interactive --tty --name test_eHmi localhost:5000/ldoktor/fedora:latest bash -c bash` Actual results: Container is not started, message: 2014/06/24 13:39:34 finalize namespace drop bounding set read /proc/1/status: bad file descriptor is in the container output. Expected results: Container should start. Additional info: There were around 14 containers running and 2 not running when this bug occurred. This bug happened to me 3 or 4 times during one week (testing docker, so the failure percentage is really low).