docker: excessive systemctl reload/restarts

[tstromberg]

I noticed this while running minikube start on a running instance:

I0318 13:50:11.255632   48225 main.go:110] libmachine: About to run SSH command:
sudo systemctl -f daemon-reload 
I0318 13:50:11.533986   48225 main.go:110] libmachine: About to run SSH command:
sudo systemctl -f enable docker
I0318 13:50:11.794742   48225 main.go:110] libmachine: About to run SSH command:
sudo systemctl daemon-reload
I0318 13:50:12.073229   48225 main.go:110] libmachine: About to run SSH command:
sudo systemctl -f restart docker

This should be sufficient, though possibly not needed either:

sudo systemctl -f daemon-reload && sudo systemctl -f restart docker

[afbjorklund]

This is normal libmachine provisioner behaviour. It does a daemon-reload before all start/restart operations.

	// systemd needs reloaded when config changes on disk; we cannot
	// be sure exactly when it changes from the provisioner so
	// we call a reload on every restart to be safe

The first one we did on purpose, I think.

        // because in kic base image we pre-install docker it already has a service file. we need to daemon-reload for the new systemd file