Let docker.service start docker services managed by puppetlabs/docker… #563
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Systemd units created by
puppetlabs/docker
defines the dependency ondocker.service
viaRequires=docker.service
stanza. This won't letdocker-mycontainer.service
service start unlessdocker.service
is running.From time to time there are situations where you stop
docker.service
(mostly due todocker
upgrades / setup changes etc.).apt-get upgrade
(or you) will stopdocker.service
,systemd
will take a care of stopping all services that statesRequires=docker.service
, docker is being upgraded and started. Unfortunatelysystemd
won't boot up thedocker-mycontainer.service
as there's no dependency definition.This PR introduces simple reverse dependency relation between docker container systemd units and
docker.service
.