On Fri, Apr 8, 2016 at 3:04 PM, Daniel J Walsh <dwa...@redhat.com> wrote:
> In docker-1.11 docker is going to be using a new daemon, containerd, as > well as runc. However docker is forcing a link between containerd and > runc. During the building of docker, docker is actually pulling the > containerd and runc packages currently installed on the box and check > summing them. The pulling just refers to when Docker is built with the Dockerfile - we instead run ./hack/make.sh which just builds Docker itself and defer to the *builder* the compilation and installation of runc and containerd (named docker-runc, docker-containerd, dockder-containerd-shim, docker-containerd-ctr) > Then docker refuses to run unless these exact versions of containerd and > runc are installed on the box. Docker does change the name of these > executables to docker-containerd and docker-runc. > Apparently Docker isn't refusing to start if the versions mismatch - it just runs but obviously they'd argue the combination isn't supported > > As we look to package these tools for Fedora, Centos and RHEL, we have to > decide whether or not we want to package multiple versions of runc so that > we can develop these at different rates or lock the versions together as > docker wants. We could patch out the checksum check and rely on rpm to > make sure the current version of docker has a late enough version of > containerd and runc, to be supported. > > Not sure what the policies of Fedora and Centos to have multiple versions > of basically the same executable installed on the system at once. > > Dan > > -- Antonio Murdaca IRC: runcom GPG: 0DE936B9
