I can't edit my post. I will try deleting Virtualbox VMs, .vagrant and .vagrantd, and the vagrantfile, then do a vanilla `vagrant init` and `vagrant up` (no modified vagrantfile like the one here <https://github.com/jwasinger/ethereum-dev-env/issues>).
On Saturday, 9 September 2017 17:28:06 UTC+10, James Ray wrote: > > I will try deleting Virtualbox VMs, .vagrant and .vagrantd, and the > vagrantfile, then reinstall Virtualbox and Vagrant, then do a vanilla > `vagrant init` and `vagrant up` (no modified vagrantfile like the one here > <https://github.com/jwasinger/ethereum-dev-env/issues>. > > On Saturday, 9 September 2017 17:15:09 UTC+10, James Ray wrote: >> >> Fresh Ubuntu 17.04 install. >> >> Install Vagrant latest version and VirtualBox. >> $ vagrant init >> >> Modify Vagrantfile with that here >> <https://github.com/jwasinger/ethereum-dev-env/issues>, and use zesty64. >> >> $ vagrant up >> >> The output ends with: >> ==> default: node-v8.3.0-linux-x64/README.md >> ==> default: cp: >> ==> default: cannot stat '/vagrant/.tmux.conf' >> ==> default: : No such file or directory >> The SSH command responded with a non-zero exit status. Vagrant >> assumes that this means the command failed. The output for this command >> should be in the log above. Please read the output to determine what >> went wrong. >> > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/f25a4744-a46f-4a2f-a40f-db713c3e6b95%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
