fix: start docker.service on-demand instead of on-boot #772
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.
Timothée Ravier from RedHat has informed us that running both Podman and Docker can result in unexpected behaviour.
This PR does not start the Docker service by default, but whenever someone interacts with the socket (e.g.
docker container ls
) thedocker.service
unit will be started automatically. This seems to replicate the current CoreOS behaviour.Please see below for tests ran to confirm if this works as expected:
To confirm this behaviour, I did the following:
docker.service
systemd unitdocker.socket
was running anddocker.service
was stoppeddocker container ls
which returned expected resultsdocker.service
was running