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.

  • What is the best approach to configure Docker for a webapp?
  • Docker with Windows
  • Running Portainer in a Docker Container with Apache 2.4 mod_proxy and basic auth
  • CircleCI: Best way to verify if docker containers are responding via HTTP
  • Unable to connect docker nginx with docker ubuntu
  • What is a Docker tag (looking for a definition)?
  • 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!

    Best,

    Mario

  • unable to create docker container on windows VM, GCP
  • Docker Compose with ASP.NET Core and PostgreSQL services
  • Pulling Docker containers from Docker hub behind a proxy results in “certificate signed by unknown authority”
  • Logging output in Docker Quickstart Terminal
  • Securing docker containers
  • Cannot authenticate to Docker in Elastic Beanstalk through S3
  • One Solution collect form web for “Cannot start container: process is killed”

    I’ve just found the problem:
    https://bugzilla.redhat.com/show_bug.cgi?id=1320601

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

    solved the problem.

    Thanks, Federkun, for help!

    Best,

    Mario

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