VM can't boot when using :hostonly networking

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

VM can't boot when using :hostonly networking

Paul Olivers
I've created a Vagrant VM, using the following settings I have configured it to use host-only networking: 

config.vm.network :hostonly, "10.10.10.101"

and to set itself up as a Chef Server (using the Opscode chef-server cookbook)

config.vm.provision :chef_solo do |chef|
    chef.cookbooks_path = "recipes/cookbooks"
    chef.roles_path     = "recipes/roles"

    chef.add_role "chef-server"
end

However, when booting the VM it stops with this error: 

~/.rvm/gems/ruby-1.9.3-p194/gems/net-scp-1.0.4/lib/net/scp.rb:385:in `await_response_state': scp: /tmp/vagrant-network-entry: Permission denied (RuntimeError)

I've added a puts to line that raises the RuntimeError, and it's caused by Vagrant trying to copy the networking config to /tmp/vagrant-network-entry on the vm. 
Any ideas what will be causing the permissions on /tmp to change and how to ensure it doesn't keep happening? 

thanks. 
Reply | Threaded
Open this post in threaded view
|

Re: VM can't boot when using :hostonly networking

Mike
Paul: Any chance this is the same issue?
https://github.com/mitchellh/vagrant/issues/1111

On Sat, Jan 19, 2013 at 5:35 PM, Paul Olivers <[hidden email]> wrote:

> I've created a Vagrant VM, using the following settings I have configured it
> to use host-only networking:
>
> config.vm.network :hostonly, "10.10.10.101"
>
> and to set itself up as a Chef Server (using the Opscode chef-server
> cookbook)
>
> config.vm.provision :chef_solo do |chef|
>     chef.cookbooks_path = "recipes/cookbooks"
>     chef.roles_path     = "recipes/roles"
>
>     chef.add_role "chef-server"
> end
>
> However, when booting the VM it stops with this error:
>
> ~/.rvm/gems/ruby-1.9.3-p194/gems/net-scp-1.0.4/lib/net/scp.rb:385:in
> `await_response_state': scp: /tmp/vagrant-network-entry: Permission denied
> (RuntimeError)
>
> I've added a puts to line that raises the RuntimeError, and it's caused by
> Vagrant trying to copy the networking config to /tmp/vagrant-network-entry
> on the vm.
> Any ideas what will be causing the permissions on /tmp to change and how to
> ensure it doesn't keep happening?
>
> thanks.