04104c3a1e
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> |
||
|---|---|---|
| .. | ||
| cloud | ||
| images | ||
| linux | ||
| binaries.md | ||
| index.md | ||
| mac.md | ||
| windows.md | ||