9a4f7f6039
- Update docker-buildx to v0.19.2. See upstream changelog online at <https://github.com/docker/buildx/releases/tag/v0.19.2>. Some notable changelogs from the last update: * <https://github.com/docker/buildx/releases/tag/v0.19.0> * <https://github.com/docker/buildx/releases/tag/v0.18.0> - Update to Go 1.22. - Add a new toggle file /etc/docker/suse-secrets-enable which allows users to disable the SUSEConnect integration with Docker (which creates special mounts in /run/secrets to allow container-suseconnect to authenticate containers with registries on registered hosts). bsc#1231348 bsc#1232999 In order to disable these mounts, just do echo 0 > /etc/docker/suse-secrets-enable and restart Docker. In order to re-enable them, just do echo 1 > /etc/docker/suse-secrets-enable and restart Docker. Docker will output information on startup to tell you whether the SUSE secrets feature is enabled or not. * 0002-SECRETS-SUSE-implement-SUSE-container-secrets.patch - Add docker-integration-tests-devel subpackage for building and running the upstream Docker integration tests on machines to test that Docker works properly. Users should not install this package. - docker-rpmlintrc updated to include allow-list for all of the integration tests package, since it contains a bunch of stuff that wouldn't normally be allowed. OBS-URL: https://build.opensuse.org/request/show/1230066 OBS-URL: https://build.opensuse.org/package/show/Virtualization:containers/docker?expand=0&rev=420
46 lines
1.6 KiB
Desktop File
46 lines
1.6 KiB
Desktop File
[Unit]
|
|
Description=Docker Application Container Engine
|
|
Documentation=http://docs.docker.com
|
|
After=network.target lvm2-monitor.service firewalld.service
|
|
# We don't use the docker socket activation, but doing this ensures that the
|
|
# docker.socket unit is alive while Docker is (docker.socket has BindsTo, so we
|
|
# only need a weak requirement to make sure starting docker.service also
|
|
# "starts" the socket service). Forcefully stopping docker.socket will not
|
|
# cause docker to die, but there's no nice workaround for that.
|
|
Wants=docker.socket
|
|
|
|
[Service]
|
|
EnvironmentFile=/etc/sysconfig/docker
|
|
|
|
# While Docker has support for socket activation (-H fd://), this is not
|
|
# enabled by default because enabling socket activation means that on boot your
|
|
# containers won't start until someone tries to administer the Docker daemon.
|
|
Type=notify
|
|
ExecStart=/usr/bin/dockerd --add-runtime oci=/usr/sbin/runc $DOCKER_OPTS
|
|
ExecReload=/bin/kill -s HUP $MAINPID
|
|
|
|
# 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=1048576
|
|
LimitNPROC=infinity
|
|
LimitCORE=infinity
|
|
|
|
# Uncomment TasksMax if your systemd version supports it.
|
|
# Only systemd 226 and above support this property.
|
|
TasksMax=infinity
|
|
|
|
# Set delegate yes so that systemd does not reset the cgroups of docker containers
|
|
# Only systemd 218 and above support this property.
|
|
Delegate=yes
|
|
|
|
# Kill only the docker process, not all processes in the cgroup.
|
|
KillMode=process
|
|
|
|
# Restart the docker process if it exits prematurely.
|
|
Restart=on-failure
|
|
StartLimitBurst=3
|
|
StartLimitInterval=60s
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|