Registrator fails on reboot

[tayzlor]

Running vagrant halt && vagrant up gives the following error -

● registrator.service - Registrator
   Loaded: loaded (/etc/systemd/system/registrator.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Mon 2016-01-11 11:46:35 GMT; 8min ago

Jan 11 11:46:34 slave1 systemd[1]: registrator.service: Unit entered failed state.
Jan 11 11:46:34 slave1 systemd[1]: registrator.service: Failed with result 'exit-code'.
Jan 11 11:46:35 slave1 systemd[1]: registrator.service: Service hold-off time over, scheduling restart.
Jan 11 11:46:35 slave1 systemd[1]: Stopped Registrator.
Jan 11 11:46:35 slave1 systemd[1]: registrator.service: Start request repeated too quickly.
Jan 11 11:46:35 slave1 systemd[1]: Failed to start Registrator.
Jan 11 11:46:35 slave1 systemd[1]: registrator.service: Unit entered failed state.
Jan 11 11:46:35 slave1 systemd[1]: registrator.service: Failed with result 'start-limit'.```

[enxebre]

probably related to #574

[tayzlor]

Couple of other services have RestartSec=20 not sure if this might affect it too as it seems to be complaining about restarting too quickly above

[tayzlor]

Looks related to consul failing to start - consul fails on a reboot as well with -

Feb 18 13:32:27 apollo-mesos-master-1 docker[1351]: Error while pulling image: Get https://index.docker.io/v1/repositories/gliderlabs/consul-server/images: dial tcp: lookup index.docker.io: Temporary failure in name resolution

These 2 issues look related

moby/moby#541
coreos/bugs#481

This might be down to our --dns configuration on the docker daemon options.

[tayzlor]

Closing via f9660d3