I removed the VM in the Virtual Box app. 

The output was still the same.

On Saturday, 9 September 2017 17:32:09 UTC+10, James Ray wrote:
>
> That didn't work.
>
> $ vagrant up
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Box 'base' could not be found. Attempting to find and 
> install...
>     default: Box Provider: virtualbox
>     default: Box Version: >= 0
> ==> default: Box file was not detected as metadata. Adding it directly...
> ==> default: Adding box 'base' (v0) for provider: virtualbox
>     default: Downloading: base
> An error occurred while downloading the remote file. The error
> message, if any, is reproduced below. Please fix this error and try
> again.
>
> Couldn't open file /home/james/base
>
>
>
>
> On Saturday, 9 September 2017 17:30:26 UTC+10, James Ray wrote:
>>
>> 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/366af8d2-9d7c-4ebd-8755-7de2a164aad0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to