Description of problem: docker run -ti busybox sh docker: Error response from daemon: Cannot start container 88132879d00c8a4c2a95e4ab9c185d4876be4e6ca95605522cb85caf0c3c1d15: [9] System error: exit status 1. Version-Release number of selected component (if applicable): docker-1.10.3-4.gitf8a9a2a.fc24.x86_64 How reproducible: always Steps to Reproduce: 1. docker run -ti busybox sh Actual results: journalctl shows Apr 20 13:10:45 localhost.localdomain systemd[1]: Started docker container 69963986c71728039aec4a08a8ea940af4cd4936d6c81e773081eb753f449e7e. Apr 20 13:10:45 localhost.localdomain oci-register-machine[5500]: 2016/04/20 13:10:45 Register machine: prestart %!d(string=69963986c71728039aec4a08a8ea940af4cd4936d6c81e773081eb753f449e7e) %!s(int=5489) /var/lib/docker/devicemapper/mnt/f6ee40cb3ee048b5cfc303a2b991d29e36a5a10f9c597ee4d23cd41ef041e1f3/rootfs Apr 20 13:10:45 localhost.localdomain oci-register-machine[5500]: 2016/04/20 13:10:45 Register machine failed: The name org.freedesktop.machine1 was not provided by any .service files Apr 20 13:10:45 localhost.localdomain systemd[1]: Stopped docker container 69963986c71728039aec4a08a8ea940af4cd4936d6c81e773081eb753f449e7e. Apr 20 13:10:45 localhost.localdomain docker[4922]: time="2016-04-20T13:10:45.928724414-04:00" level=warning msg="exit status 2" Apr 20 13:10:45 localhost.localdomain oci-systemd-hook[5531]: systemdhook <debug>: Skipping as container command is /bin/sh, not init or systemd Apr 20 13:10:45 localhost.localdomain oci-register-machine[5532]: 2016/04/20 13:10:45 Register machine: poststop %!d(string=69963986c71728039aec4a08a8ea940af4cd4936d6c81e773081eb753f449e7e) %!s(int=0) /var/lib/docker/devicemapper/mnt/f6ee40cb3ee048b5cfc303a2b991d29e36a5a10f9c597ee4d23cd41ef041e1f3/rootfs Apr 20 13:10:45 localhost.localdomain oci-register-machine[5532]: 2016/04/20 13:10:45 TerminateMachine failed: The name org.freedesktop.machine1 was not provided by any .service files Apr 20 13:10:45 localhost.localdomain kernel: docker0: port 1(vethcb37e4e) entered disabled state Expected results: container to run and get a shell Additional info: Solution was `dnf install systemd-container`, so I suspect that docker in F24 needs that as a dependency yet? (I don't see any issues tracking this yet, oddly. I've made good use of a number of docker related BZ reports and good troubleshooting tips in them - Thank you. So I had worked past some issues and ruled out others as maybe "circle back to". That left the error above. I tracked the steps for the recent introduction of oci-register-machine, and then read a bit about machined and realized that machinectl wasn't installed here. I tried the package that provides it and that got the container to run.)
This is an oci-register-machine issue.
Fixed in oci-register-machine-0-1.1.git7d4ce65.fc24
*** Bug 1334588 has been marked as a duplicate of this bug. ***
Can we get this into f24 final release?
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.