toolshed/docker-cli
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove docker.socket from rpm based systems

Browse Source 
Fixes #23981

The selinux issue we are seeing in the report is related to the socket
file for docker and nothing else. By removing the socket docker starts
up correctly.

However, there is another motivation for removing socket activation from
docker's systemd files and that is because when you have daemons running
with --restart always whenever you have a host reboot those daemons
will not be started again because the docker daemon is not started by
systemd until a request comes into the docker API.

Leave it for deb based systems because everything is working correctly
for both socket activation and starting normally at boot.

Signed-off-by: Michael Crosby <crosbymichael@gmail.com>
Upstream-commit: 04104c3a1e6cad30cb41b762e8832215466c0e95
Component: engine
This commit is contained in:
Michael Crosby
2016-07-18 16:37:29 -07:00
parent 32c154633c
commit 02e14246d7
3 changed files with 34 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
components/engine/docs/installation/linux/fedora.md
View File

@ -60,9 +60,9 @@ There are two ways to install Docker Engine. You can install with the `dnf` pac
$ sudo dnf install docker-engine
5. Enable the socket and service.
5. Enable the service.
$ sudo systemctl enable docker.socket docker.service
$ sudo systemctl enable docker.service
6. Start the Docker daemon.
@ -113,9 +113,9 @@ There are two ways to install Docker Engine. You can install with the `dnf` pac
This script adds the `docker.repo` repository and installs Docker.
4. Enable the socket and service.
4. Enable the service.
$ sudo systemctl enable docker.socket docker.service
$ sudo systemctl enable docker.service
5. Start the Docker daemon.