kotovalexarian-likes-github/moby--moby
1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
Code Releases Activity
moby--moby/contrib/init/systemd/docker.service

42 lines
1.5 KiB
SYSTEMD
Raw Normal View History

Add systemd files, add containerd-proxy config Signed-off-by: Eli Uriegas <eli.uriegas@docker.com>
2018-08-14 16:30:22 -04:00
[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
Set containerd to be a systemd bind for docker The daemon won't actually start without containerd Signed-off-by: Eli Uriegas <eli.uriegas@docker.com>
2018-08-20 17:13:52 -04:00
BindsTo=containerd.service
After=network-online.target firewalld.service
Wants=network-online.target
Add systemd files, add containerd-proxy config Signed-off-by: Eli Uriegas <eli.uriegas@docker.com>
2018-08-14 16:30:22 -04:00
[Service]
# Install containerd-shim-process if it's not already installed
Revive pre / post steps, update offline location Signed-off-by: Eli Uriegas <eli.uriegas@docker.com>
2018-08-15 19:13:21 -04:00
ExecStartPre=/usr/libexec/containerd-offline-installer /var/lib/containerd-offline-installer/containerd-shim-process.tar docker.io/docker/containerd-shim-process
systemd: add "Delegate=yes" to docker's service file We need to add delegate yes to docker's service file so that it can manage the cgroups of the processes that it launches without systemd interfering with them and moving the processes after it is reloaded. Delegate= Turns on delegation of further resource control partitioning to processes of the unit. For unprivileged services (i.e. those using the User= setting), this allows processes to create a subhierarchy beneath its control group path. For privileged services and scopes, this ensures the processes will have all control group controllers enabled. This is the proper fix for issue moby/moby#20152 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2018-08-31 06:53:49 -04:00
# the default is not to use systemd for cgroups because the delegate issues still
# exists and systemd currently does not support the cgroup feature set required
# for containers run by docker
Add systemd files, add containerd-proxy config Signed-off-by: Eli Uriegas <eli.uriegas@docker.com>
2018-08-14 16:30:22 -04:00
ExecStart=/usr/bin/dockerd
Add post-stop Signed-off-by: Michael Crosby <crosbymichael@gmail.com>
2018-08-28 13:51:21 -04:00
ExecStopPost=/usr/bin/dockerd post-stop
Some changes to get this working on CentOS 7 Old versions of things on CentOS 7 strike again! infinity is not a thing for TimeoutSec on systemd < 229 Signed-off-by: Eli Uriegas <eli.uriegas@docker.com>
2018-08-16 00:03:40 -04:00
TimeoutSec=0
added RestartSec Signed-off-by: Andrew Hsu <andrewhsu@docker.com> (cherry picked from commit 51879873897afe298cbb736acef34b5a0b500424) Signed-off-by: Andrew Hsu <andrewhsu@docker.com>
2018-08-24 18:40:02 -04:00
RestartSec=2
Round out systemd for RPM packaging Signed-off-by: Eli Uriegas <eli.uriegas@docker.com>
2018-08-14 21:42:10 -04:00
Restart=always
# On RPM Based distributions PATH isn't defined so we define it here
# /opt/containerd/bin is in front so dockerd grabs the correct runc binary
Environment="PATH=/opt/containerd/bin:/sbin:/usr/bin:/usr/local/bin:$PATH"
Add systemd files, add containerd-proxy config Signed-off-by: Eli Uriegas <eli.uriegas@docker.com>
2018-08-14 16:30:22 -04:00
systemd: set Limit* to infinity There is a not-insignificant performance overhead for all containers (if containerd is a child of Docker, which is the current setup) if systemd sets rlimits on the main Docker daemon process (because the limits propogate to all children). Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2018-08-31 06:45:07 -04:00
# Having non-zero Limit*s causes performance problems due to accounting overhead
# in the kernel. We recommend using cgroups to do container-local accounting.
LimitNOFILE=infinity
LimitNPROC=infinity
systemd: no limit on core size set LimitCORE=infinity to ensure complete core creation, allows extraction of as much information as possible. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2018-08-31 06:43:32 -04:00
LimitCORE=infinity
systemd: don't limit tasks Systemd sets a default of 512 tasks, which is far too low to run many containers. Note that TasksMax is only supported on systemd 226 and above. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2018-08-31 06:50:05 -04:00
# Comment TasksMax if your systemd version does not supports it.
# Only systemd 226 and above support this option.
TasksMax=infinity
systemd: add "Delegate=yes" to docker's service file We need to add delegate yes to docker's service file so that it can manage the cgroups of the processes that it launches without systemd interfering with them and moving the processes after it is reloaded. Delegate= Turns on delegation of further resource control partitioning to processes of the unit. For unprivileged services (i.e. those using the User= setting), this allows processes to create a subhierarchy beneath its control group path. For privileged services and scopes, this ensures the processes will have all control group controllers enabled. This is the proper fix for issue moby/moby#20152 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2018-08-31 06:53:49 -04:00
# set delegate yes so that systemd does not reset the cgroups of docker containers
Delegate=yes
systemd: set systemd KillMode Change the kill mode to process so that systemd does not kill container processes when the daemon is shutdown but only the docker daemon Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2018-08-31 06:55:39 -04:00
# kill only the docker process, not all processes in the cgroup
KillMode=process
Add systemd files, add containerd-proxy config Signed-off-by: Eli Uriegas <eli.uriegas@docker.com>
2018-08-14 16:30:22 -04:00
[Install]
WantedBy=multi-user.target
Copy permalink