Open Random-Liu opened 5 years ago
I reproduced this behaviour with 19.03 as well...
When the containerd
executable is killed, the containerd
service goes into the inactive (dead)
state and so does the docker
service.
Just starting the containerd
service with systemctl start containerd
is not enough to get docker going again. Need to also do a systemctl start docker
to get the service back up.
@seemethere @kolyshkin is there a systemd.unit directive that can gracefully have the docker
service start up again if the only reason why it was down was because the containerd
service went down? we may need a healthcheck to accomplish this. dunno, thinking out loud here.
Now that containerd has Restart=always
in the unit file, we just need to change BindTo=containerd.service
to Requires=containerd.service
in the Docker unit file, as in my pull request.
Expected behavior
After containerd is temporarily killed and restarted, docker should continue working.
Actual behavior
Once containerd is killed, docker will be stopped by systemd. And systemd won't restart docker anymore, "when the death of the process is a result of systemd operation (e.g. service stop or restart)" (See https://github.com/systemd/systemd/issues/2824)
Steps to reproduce the behavior
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.) GCE