https://bugzilla.redhat.com/show_bug.cgi?id=1102751
Bug ID: 1102751 Summary: Got "Error running removeDevice" after kill -9 docker Product: Fedora Version: 20 Component: docker-io Assignee: lsm5@redhat.com Reporter: mfojtik@redhat.com QA Contact: extras-qa@fedoraproject.org CC: admiller@redhat.com, golang@lists.fedoraproject.org, lsm5@redhat.com, mattdm@redhat.com, mgoldman@redhat.com, s@shk.io, vbatts@redhat.com
Description of problem:
While I was playing with Docker today, I found interesting behavior:
When you 'kill -9' the 'docker -d' process, then this happens:
1. The 'docker -d' process gets killed ;-) 2. All containers gets killed 3. The 'docker -d' restarts, because of Restart=on-failure
Now, while all this is expected and OK, I get this when I tried to 'restart' the container that was killed in 2):
May 29 13:24:56 ip-10-146-193-102 systemd[1]: Starting Container origin-db-1... May 29 13:24:56 ip-10-146-193-102 sh[19731]: Reusing b80104263de02f39bbc6d742c977ddadecb0660f5c50386eaf1cf645f3515b9c May 29 13:25:07 ip-10-146-193-102 docker[19739]: Error: Cannot destroy container origin-db-1: Driver devicemapper failed to remove root filesystem e536cf328e0083e2414c750434deb1127517d00399fddac84903825d6f003787: Error running removeDevice May 29 13:25:07 ip-10-146-193-102 docker[19739]: 2014/05/29 13:25:07 Error: failed to remove one or more containers May 29 13:25:07 ip-10-146-193-102 gear[21193]: user: unknown user ctr-origin-db-1 May 29 13:25:09 ip-10-146-193-102 docker[21192]: 2014/05/29 13:25:09 Error: Cannot start container bd1a88a35e84ef6d71fa3e1df0b4e2998318dfed6d60fd3ae381567fff2ac2a3: Cannot find child for /origin-db-1 May 29 13:25:09 ip-10-146-193-102 systemd[1]: ctr-origin-db-1.service: main process exited, code=exited, status=1/FAILURE
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Start up some containers 2. kill -9 (the 'docker -d' process pid) 3. Try to start the dead container again 4. Get the error above.
Actual results:
Expected results:
Containers should be successfully started back.
Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1102751
Daniel Walsh dwalsh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dwalsh@redhat.com Assignee|lsm5@redhat.com |alexl@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1102751
Daniel Walsh dwalsh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |mfojtik@redhat.com Flags| |needinfo?(mfojtik@redhat.co | |m)
--- Comment #1 from Daniel Walsh dwalsh@redhat.com --- Does this still happen with docker-1.0?
https://bugzilla.redhat.com/show_bug.cgi?id=1102751
Daniel Walsh dwalsh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |MODIFIED
--- Comment #2 from Daniel Walsh dwalsh@redhat.com --- Reopen if not.
https://bugzilla.redhat.com/show_bug.cgi?id=1102751
--- Comment #3 from Fedora End Of Life endoflife@fedoraproject.org --- This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
https://bugzilla.redhat.com/show_bug.cgi?id=1102751
Daniel Walsh dwalsh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |CLOSED Resolution|--- |CURRENTRELEASE Last Closed| |2015-05-29 08:03:24
golang@lists.fedoraproject.org