Cannot start container: process is killed

my containers are killed on a new installation of Fedora 24 atomic:

#docker run -ti nginx /bin/bash

docker: Error response from daemon: Cannot start container f24104b29f7f1f1614024414e8346e1a98c722c027f4122e6c70f7ace0cc5353: [9] System error: exit status 1.

After some debugging session, I think the process gets killed right after trying to assign an address on network bridge (see docker daemon logs in the next links). But I have no idea why is that nor how to debug further.

  • Docker 1.9 overlay network - access from host
  • Find out to which removed docker container a volume belonged to
  • Error during compilation / installation of libcontainer due to custom-build kernel
  • Only first line being read in Dockerfile
  • Ubuntu run service in foreground
  • Disable logging for one container in Docker-Compose
  • Some additional info is reported here:

    • SELinux is disabled:
      • bash-4.3# getenforce -> Permissive
    • docker info
    • docker daemon log in debug mode. At line 9 it receives the KILL signal.

    Any help would really be appreciated!



  • Docker in Vagrant issuing : Warning: Connection refused. Retrying
  • cant connect to docker daemon - eclipse che
  • Redis Exited While Run With Persistent Data In Boot2Docker
  • Restrict docker engine to a single GPU
  • automatically add the release tag to my build from git tag
  • Docker External File Access Not in /Users/ on OSX
  • One Solution collect form web for “Cannot start container: process is killed”

    I’ve just found the problem:

    Adding the systemd flag to the launch script of the daemon:
    –exec-opt native.cgroupdriver=systemd

    solved the problem.

    Thanks, Federkun, for help!



    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.