Disable containerd from starting up at boot #8621
Merged
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.
Saves us having to restart docker later on (see f2ea21a)
Tested with docker and with containerd runtimes
With the currently generated
minikube.service
, the default is to run with/run/docker/containerd/containerd.sock
It is only when containerd is explicitly selected (and not docker), that we want to use
/run/containerd/containerd.sock
Note that it will just disable the containerd.service
There will still be a containerd process running...
Closes #8618