--- Comment #5 from Daniel Walsh <dwalsh(a)redhat.com> ---
docker socket activation breaks the ability for docker to start services
automatically. Since docker mimics some of the functionality of systemd, users
setting a container to start automatically when the machine reboots would not
work with docker starting on socket activation, since no process would be
connecting to the /run/docker.sock to trigger docker to start and start its
If you don't have these types of containers you should be able to configure
docker to autostart, but we don't want this by default.
You are receiving this mail because:
You are on the CC list for the bug.