moby/contrib/init
Tianon Gravi a985655ac4 Move containerd.service from Requires= to Wants=
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 <admwiggin@gmail.com>
Signed-off-by: Anca Iordache <anca.iordache@docker.com>
2021-07-12 10:06:35 +00:00
..
openrc run shfmt 2020-03-03 12:27:49 +09:00
systemd Move containerd.service from Requires= to Wants= 2021-07-12 10:06:35 +00:00
sysvinit-debian run shfmt 2020-03-03 12:27:49 +09:00
sysvinit-redhat run shfmt 2020-03-03 12:27:49 +09:00
upstart contrib: remove REVIEWERS files 2020-06-24 12:12:09 +02:00