After updating docker to 1.12, starting existing containers will fail with "docker-runc not installed"

Solution Unverified - Updated -


  • After upgrading docker 1.10 to 1.12, docker is started with the following parameters:

    # ps -ef | grep docker
    root     21373     1  0 09:31 ?        00:00:00 /usr/bin/dockerd-current --add-runtime docker-runc=/usr/libexec/docker/docker-runc-current --default-runtime=docker-runc --authorization-plugin=rhel-push-plugin --exec-opt native.cgroupdriver=systemd --userland-proxy-path=/usr/libexec/docker/docker-proxy-current -H tcp:// -H unix:///var/run/docker.sock --log-driver=journald --storage-driver overlay --add-registry
    root     21389 21373  0 09:31 ?        00:00:00 /usr/bin/docker-containerd-current -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --shim docker-containerd-shim --metrics-interval=0 --start-timeout 2m --state-dir /var/run/docker/libcontainerd/containerd --runtime docker-runc --runtime-args --systemd-cgroup=true
    root     25067     1  0  2016 ?        00:03:08 /usr/libexec/docker/rhel-push-plugin
  • Starting a previously running container does not work:

    $ docker start <container>
    Error response from daemon: shim error: docker-runc not installed on system
    Error: failed to start containers: <container>
  • Linking the docker-runc-latest binary to docker-runc fixes the issue


  • Red Hat Enterprise Linux (RHEL) 7.3
  • docker-1.12.5-14.el7.x86_64.rpm

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content