containerd service is running on docker driver with docker run time

[medyagh]

While trying to figure out why minikube soft start on docker driver takes longer than VM (#7432)

I noticed on docker driver the containerd service is running but in VM its NOT !

on docker driver:

docker@minikube:~$ sudo systemctl status containerd
● containerd.service - containerd container runtime
   Loaded: loaded (/etc/systemd/system/containerd.service; disabled; vendor preset: enabled)
   Active: active (running) since Sun 2020-04-05 10:21:11 UTC; 44s ago
     Docs: https://containerd.io

on VM hyperkit:

● containerd.service - containerd container runtime
   Loaded: loaded (/usr/lib/systemd/system/containerd.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
     Docs: https://containerd.io

[afbjorklund]

Since dockerd depends on containerd, I think that this situation is normal ?

Previously it had custom docker-runc and docker-containerd, but not anymore.

https://docs.docker.com/engine/release-notes/18.09/#important-notes-about-this-release-1

In Docker versions prior to 18.09, containerd was managed by the Docker engine daemon. In Docker Engine 18.09, containerd is managed by systemd.

[medyagh]

minikube/pkg/provision/ubuntu.go

Line 78 in 792ca8e

BindsTo=containerd.service

I just saw this that only for ubuntu provisioner (kic provisioner) we add bind to containerd and when I remove it it will get stuck in kubeadm init.

@afbjorklund why in VM world we dont have containerd service running but only in kic world ?

also if docker service has to have containerd service running, then we need to disable the logic to DISABLE other container run times.... (because for docker it will disable containerd (which api server is running on it) that willi cause an un-needed False needsReset()
that will make kic soft start (start and then start) very slow compared to VM

what do youu think we should do about it ?

[medyagh]

from minikube logs for docker driver on a soft start I see that it is trying to stop other container run time services

I0405 04:32:31.291549   38471 kic_runner.go:91] Run: curl -sS -m 2 https://k8s.gcr.io/
I0405 04:32:31.293213   38471 kic_runner.go:91] Run: sudo systemctl is-active --quiet service containerd
I0405 04:32:31.519786   38471 kic_runner.go:91] Run: sudo systemctl stop -f containerd

i believe the problem is on ubuntu I install docker for ubuntu which requires containerd

but in the VM the buildroot does not rquired containerd

[afbjorklund]

@afbjorklund why in VM world we dont have containerd service running but only in kic world ?

The VM has two different containerd running:

• /run/docker/containerd/containerd.sock

/usr/lib/systemd/system/docker.service
containerd --config /var/run/docker/containerd/containerd.toml --log-level info

• /run/containerd/containerd.sock

/usr/lib/systemd/system/containerd.service
/usr/bin/containerd --root /mnt/sda1/var/lib/containerd

That is, Docker will start containerd itself if not running...

See libcontainerd/supervisor/remote_daemon.go

[afbjorklund]

The minikube docker.service has this configuration:

ExecStart=/usr/bin/dockerd -H tcp://0.0.0.0:2376 -H unix:///var/run/docker.sock --default-ulimit=nofile=1048576:1048576 --tlsverify --tlscacert /etc/docker/ca.pem --tlscert /etc/docker/server.pem --tlskey /etc/docker/server-key.pem --label provider=virtualbox --insecure-registry 10.96.0.0/12

The ubuntu docker.service has this configuration:

ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

[tstromberg]

Can we close this because the mystery is solved?