https://bugzilla.redhat.com/show_bug.cgi?id=1112700
Bug ID: 1112700 Summary: docker container not started, bad file descriptor Product: Fedora Version: 20 Component: docker-io Assignee: lsm5@redhat.com Reporter: ldoktor@redhat.com QA Contact: extras-qa@fedoraproject.org CC: admiller@redhat.com, golang@lists.fedoraproject.org, hushan.jia@gmail.com, lsm5@redhat.com, mattdm@redhat.com, mgoldman@redhat.com, s@shk.io, vbatts@redhat.com
Created attachment 911745 --> https://bugzilla.redhat.com/attachment.cgi?id=911745&action=edit /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).
https://bugzilla.redhat.com/show_bug.cgi?id=1112700
--- Comment #1 from Marek Goldmann mgoldman@redhat.com --- I see this too. When I execute the same command one more time - it works.
https://bugzilla.redhat.com/show_bug.cgi?id=1112700
Lokesh Mandvekar lsm5@switzerlandmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lsm5@switzerlandmail.ch Assignee|lsm5@redhat.com |lsm5@switzerlandmail.ch
https://bugzilla.redhat.com/show_bug.cgi?id=1112700
Lokesh Mandvekar lsm5@switzerlandmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED See Also| |https://bugzilla.redhat.com | |/show_bug.cgi?id=1109533
--- Comment #2 from Lokesh Mandvekar lsm5@switzerlandmail.ch --- NVR docker-io-1.0.0-3 should take care of this. Let me know if that still occurs though
https://bugzilla.redhat.com/show_bug.cgi?id=1112700
Daniel Walsh dwalsh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |MODIFIED CC| |dwalsh@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1112700
Lukas Doktor ldoktor@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |VERIFIED
--- Comment #3 from Lukas Doktor ldoktor@redhat.com --- Hi Daniel, I executed lots of containers with the docker-1.0.0-10.el7.x86_64 without seeing this issue. I guess it's taken care of. Thanks.
https://bugzilla.redhat.com/show_bug.cgi?id=1112700
Lokesh Mandvekar lsm5@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|VERIFIED |CLOSED Resolution|--- |ERRATA Last Closed| |2014-07-23 20:07:32
--- Comment #4 from Lokesh Mandvekar lsm5@fedoraproject.org --- Closing this one...NVR docker-io-1.0.0-3 is already in stable. Also see Bug 1109533 if needed
golang@lists.fedoraproject.org