coreos / coreos-kubernetes

CoreOS Container Linux+Kubernetes documentation & Vagrant installers
https://coreos.com/kubernetes/docs/latest/
Apache License 2.0
1.1k stars 466 forks source link

vagrant up fails with "sed: can't read /usr/lib/systemd/system/docker.service: No such file or directory" #903

Closed alanbirtles closed 7 years ago

alanbirtles commented 7 years ago

running "vagrant up" results in:

Bringing machine 'e1' up with 'virtualbox' provider...
Bringing machine 'c1' up with 'virtualbox' provider...
Bringing machine 'w1' up with 'virtualbox' provider...
==> e1: Checking if box 'coreos-alpha' is up to date...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

sed -e 's/\[Service\]/[Service]\nEnvironmentFile=-\/etc\/default\/docker/g' /usr/lib/systemd/system/docker.service > /tmp/docker.service

Stdout from the command:

Stderr from the command:

sed: can't read /usr/lib/systemd/system/docker.service: No such file or directory

I'm using vagrant 1.9.7 on Centos 7 and am following these instructions https://coreos.com/kubernetes/docs/latest/kubernetes-on-vagrant.html

alanbirtles commented 7 years ago

caused by https://github.com/tmatilai/vagrant-proxyconf/issues/162