Currently it seems vagrant-proxyconf assumes either upstart or init scripts for docker, thus it fails
Vagrant assumes that this means the command failed!
service docker restart || /etc/init.d/docker restart
Stdout from the command:
Stderr from the command:
bash: line 2: service: command not found
bash: line 2: /etc/init.d/docker: No such file or directory
Currently it seems vagrant-proxyconf assumes either upstart or init scripts for docker, thus it fails
On coreOS as it is using systemd.
Full debug log is here https://gist.github.com/btrepp/a52650dfd3dc5ba1fdae