https://bugzilla.redhat.com/show_bug.cgi?id=1166082
--- Comment #8 from Dusty Mabe <[email protected]> --- Some new information has come to light. I think (long term) we should somehow get the docker service enabled as when users see that it is disabled it raises questions and we get bug reports. It is expected behavior that a daemon should be running before a user can use the service (i.e. libvirtd must be running in order to use virsh). Short term this isn't really a problem though (as far as functionality goes). The docker executable will start the docker daemon if it isn't already running on the system. This means anytime you execute docker it will start the docker daemon. For this reason the service doesn't really need to be enabled at all. I verified that adding a systemd unit file (i.e. /etc/systemd/system/owncloud.service) to run a docker container on boot also started the docker daemon. An interesting note about this though: typically in my unit file I have "After=docker.service". I can't do that in this case unless I enable the service. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ golang mailing list [email protected] https://lists.fedoraproject.org/mailman/listinfo/golang
