cannot stat '/vagrant/.tmux.conf'

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

cannot stat '/vagrant/.tmux.conf'

James Ray
Fresh Ubuntu 17.04 install.

Install Vagrant latest version and VirtualBox.
$ vagrant init

Modify Vagrantfile with that here, 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/26a914a1-af9f-4ca8-b34b-d27bfc68e0e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: cannot stat '/vagrant/.tmux.conf'

James Ray
Related:

https://github.com/mitchellh/vagrant/issues/5951

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here, 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/647e59fa-02e9-46ad-aa78-b716ecb7a8d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: cannot stat '/vagrant/.tmux.conf'

James Ray
In reply to this post by James Ray
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.

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here, 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/8603c928-67e9-419c-bcd8-d8d47cd81046%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: cannot stat '/vagrant/.tmux.conf'

James Ray
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).

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here.

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here, 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 [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|

Re: cannot stat '/vagrant/.tmux.conf'

James Ray
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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here).

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here.

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here, 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/2652e90a-71cc-4d43-ac34-da6012383ff7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: cannot stat '/vagrant/.tmux.conf'

James Ray
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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here).

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here.

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here, 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 [hidden email].
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 | Threaded
Open this post in threaded view
|

Re: cannot stat '/vagrant/.tmux.conf'

James Ray
Related: https://stackoverflow.com/questions/23874260/error-when-trying-vagrant-up

On Saturday, 9 September 2017 17:36:40 UTC+10, James Ray wrote:
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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here).

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here.

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here, 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/2c220d37-ba09-4aaa-aea0-5cb548ecc05f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: cannot stat '/vagrant/.tmux.conf'

James Ray
I made the same mistake that I've made before, you can't use `vagrant init` then press enter, you have to have `vagrant init <insert box name>`, e.g. `vagrant init ubuntu/zesty64`.

On Saturday, 9 September 2017 17:47:39 UTC+10, James Ray wrote:
Related: <a href="https://stackoverflow.com/questions/23874260/error-when-trying-vagrant-up" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F23874260%2Ferror-when-trying-vagrant-up\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEd8Y1IIyZM2Bo1EkTDwF97JQpo2Q&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F23874260%2Ferror-when-trying-vagrant-up\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEd8Y1IIyZM2Bo1EkTDwF97JQpo2Q&#39;;return true;">https://stackoverflow.com/questions/23874260/error-when-trying-vagrant-up

On Saturday, 9 September 2017 17:36:40 UTC+10, James Ray wrote:
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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here).

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here.

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here, 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/3c0577fc-d8ba-4341-8837-d3ebb689a9b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: cannot stat '/vagrant/.tmux.conf'

James Ray
Seems like it worked.

default: /vagrant => /home/james

On Saturday, 9 September 2017 17:49:34 UTC+10, James Ray wrote:
I made the same mistake that I've made before, you can't use `vagrant init` then press enter, you have to have `vagrant init <insert box name>`, e.g. `vagrant init ubuntu/zesty64`.

On Saturday, 9 September 2017 17:47:39 UTC+10, James Ray wrote:
Related: <a href="https://stackoverflow.com/questions/23874260/error-when-trying-vagrant-up" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F23874260%2Ferror-when-trying-vagrant-up\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEd8Y1IIyZM2Bo1EkTDwF97JQpo2Q&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F23874260%2Ferror-when-trying-vagrant-up\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEd8Y1IIyZM2Bo1EkTDwF97JQpo2Q&#39;;return true;">https://stackoverflow.com/questions/23874260/error-when-trying-vagrant-up

On Saturday, 9 September 2017 17:36:40 UTC+10, James Ray wrote:
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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here).

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here.

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here, 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/edcc2980-189f-4470-8a3a-22f4e21a02c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: cannot stat '/vagrant/.tmux.conf'

James Ray
So I tried again with the modified vagrantfile here, but the attached output seems to be the same as previously.

On Saturday, 9 September 2017 18:00:37 UTC+10, James Ray wrote:
Seems like it worked.

default: /vagrant => /home/james

On Saturday, 9 September 2017 17:49:34 UTC+10, James Ray wrote:
I made the same mistake that I've made before, you can't use `vagrant init` then press enter, you have to have `vagrant init <insert box name>`, e.g. `vagrant init ubuntu/zesty64`.

On Saturday, 9 September 2017 17:47:39 UTC+10, James Ray wrote:
Related: <a href="https://stackoverflow.com/questions/23874260/error-when-trying-vagrant-up" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F23874260%2Ferror-when-trying-vagrant-up\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEd8Y1IIyZM2Bo1EkTDwF97JQpo2Q&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F23874260%2Ferror-when-trying-vagrant-up\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEd8Y1IIyZM2Bo1EkTDwF97JQpo2Q&#39;;return true;">https://stackoverflow.com/questions/23874260/error-when-trying-vagrant-up

On Saturday, 9 September 2017 17:36:40 UTC+10, James Ray wrote:
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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here).

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here.

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here, 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/fb685d5b-e307-49e0-8975-80085f9c2fb7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

vagrantUpWithEthDevEnv.txt (709K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: cannot stat '/vagrant/.tmux.conf'

James Ray
https://github.com/mitchellh/vagrant/issues/8956

On Saturday, 9 September 2017 18:47:10 UTC+10, James Ray wrote:
So I tried again with the modified vagrantfile <a href="https://github.com/jwasinger/ethereum-dev-env/blob/master/ethereumjs/Vagrantfile" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fblob%2Fmaster%2Fethereumjs%2FVagrantfile\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFwKhFMT25XSFgYjSp3c9zpFhNyXg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fblob%2Fmaster%2Fethereumjs%2FVagrantfile\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFwKhFMT25XSFgYjSp3c9zpFhNyXg&#39;;return true;">here, but the attached output seems to be the same as previously.

On Saturday, 9 September 2017 18:00:37 UTC+10, James Ray wrote:
Seems like it worked.

default: /vagrant => /home/james

On Saturday, 9 September 2017 17:49:34 UTC+10, James Ray wrote:
I made the same mistake that I've made before, you can't use `vagrant init` then press enter, you have to have `vagrant init <insert box name>`, e.g. `vagrant init ubuntu/zesty64`.

On Saturday, 9 September 2017 17:47:39 UTC+10, James Ray wrote:
Related: <a href="https://stackoverflow.com/questions/23874260/error-when-trying-vagrant-up" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F23874260%2Ferror-when-trying-vagrant-up\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEd8Y1IIyZM2Bo1EkTDwF97JQpo2Q&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F23874260%2Ferror-when-trying-vagrant-up\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEd8Y1IIyZM2Bo1EkTDwF97JQpo2Q&#39;;return true;">https://stackoverflow.com/questions/23874260/error-when-trying-vagrant-up

On Saturday, 9 September 2017 17:36:40 UTC+10, James Ray wrote:
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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here).

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here.

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 <a href="https://github.com/jwasinger/ethereum-dev-env/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjwasinger%2Fethereum-dev-env%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEqFBdHtZAEtpqAqFoF7JBAnZkl6A&#39;;return true;">here, 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/5f8bd20e-a90d-4526-ad08-fc2714674c0f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.