Bug 1112700 - docker container not started, bad file descriptor
Summary: docker container not started, bad file descriptor
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: docker-io
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lokesh Mandvekar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-24 13:56 UTC by Lukáš Doktor
Modified: 2014-07-24 00:07 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-24 00:07:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
/var/log/messages output (41.93 KB, text/plain)
2014-06-24 13:56 UTC, Lukáš Doktor
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1109533 0 unspecified CLOSED finalize namespace errors with docker run 2021-02-22 00:41:40 UTC

Internal Links: 1109533

Description Lukáš Doktor 2014-06-24 13:56:22 UTC
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).

Comment 1 Marek Goldmann 2014-06-24 14:39:33 UTC
I see this too. When I execute the same command one more time - it works.

Comment 2 Lokesh Mandvekar 2014-06-25 04:25:40 UTC
NVR docker-io-1.0.0-3 should take care of this. Let me know if that still occurs though

Comment 3 Lukáš Doktor 2014-07-18 08:44:15 UTC
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.

Comment 4 Lokesh Mandvekar 2014-07-24 00:07:32 UTC
Closing this one...NVR docker-io-1.0.0-3 is already in stable. Also see Bug 1109533 if needed


Note You need to log in before you can comment on or make changes to this bug.