-
Notifications
You must be signed in to change notification settings - Fork 161
Move containerd.service from Requires= to Wants= #512
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
love the typo; its on theme 😇 |
3865e06 to
1e9d40a
Compare
I have no idea what you're talking about!! (it's fixed 😇 ❤️) |
|
I have verified that with this change, I'm able to |
|
Thanks! I actually recalled I left this as a comment for follow up on #508
|
thaJeztah
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
@tianon looks like this needs a rebase 😅 |
Per the systemd.unit documentation: > If this unit gets activated, the units listed will be activated as well. If one of the other units fails to activate, and an ordering dependency After= on the failing unit is set, this unit will not be started. Besides, with or without specifying After=, this unit will be stopped if one of the other units is explicitly stopped. > > Often, it is a better choice to use Wants= instead of Requires= in order to achieve a system that is more robust when dealing with failing services. This should also be generally "safe" given we added `--containerd=/run/containerd/containerd.sock` to the flags we pass to `dockerd`. Signed-off-by: Tianon Gravi <[email protected]>
|
Closing here, because the file was moved back to the moby repository. |
Per the systemd.unit documentation:
This should also be generally "safe" given we added
--containerd=/run/containerd/containerd.sockto the flags we pass todockerd.See #511 (comment).