This repository has been archived by the owner on Sep 26, 2021. It is now read-only.
Missing KillMode=process in docker.service cause live-restore fail.
#3963
Labels
Comments
twang2218
added a commit
to twang2218/machine
that referenced
this issue
Jan 25, 2017
Using systemd drop-in for the configuration is better for inherit the package default settings, without the need of sync the settings between 2 projects. Fixes docker#3963 Signed-off-by: Tao Wang <twang2218@gmail.com>
afbjorklund
pushed a commit
to minikube-machine/machine
that referenced
this issue
Jun 10, 2023
Using systemd drop-in for the configuration is better for inherit the package default settings, without the need of sync the settings between 2 projects. Fixes docker/machine#3963 Signed-off-by: Tao Wang <twang2218@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As discussed in moby/moby#30308, I created a Digital Ocean droplet, with Ubuntu 16.04 on it, and the
live-restoreis failed to use.It becasue the
/etc/systemd/system/multi-user.target.wants/docker.servicedidn't contain the same settings in the https://github.com/docker/docker/blob/master/contrib/init/systemd/docker.service , especially, in this case, theKillMode=processis missing, which is the reasonlive-restoredoesn't work in the docker host created bydocker-machine.Should we consider using systemd drop-in settings instead? So most other settings can be inherited from the default package settings.
The text was updated successfully, but these errors were encountered: