H ... so with an uninstall and subsequent reinstall of both VirtualBox
and vagrant and following my notes to the letter, I've just created another
VirtualBox guest and packaged it up as a base box - it works flawlessly,
including the addition of config.ssh.username and .password.
Very,
the "curl -L ..." worked just fine. Oddly enough, I went through and
reinstalled both vagrant and virtualbox before reading your post Alvaro.
One thing I do notice, working on my Ubuntu desktop: there are two ways of
loading VirtualBox, with differing results:
1. Dash > Applications >
On Tue, May 31, 2016 at 10:07 AM, BRIT <
buildingreliableitsoluti...@gmail.com> wrote:
> for cmd.exe
> set VAGRANT_LOG=debug
>
> for bash
> export VAGRANT_LOG=debug
>
> then:
>
> vagrant up
>
> And share the generated text over a gist. (gist.github.com)
Hello, are you installing Vagrant from
Hello,
Are you behind any firewall or proxy that may be stopping this to work?
Or do you need to define a proxy?
Please try this:
curl -L https://atlas.hashicorp.com/cbednarski/ubuntu-1404.json
If that works, then I would suggest reinstall vagrant on that machine.
If after reinstall the issue
- vagrant version 1.8.1
- vagrant-share (1.1.5, system)
Log file is attached. Editing the file with the private network worked
just fine. This hasn't been the issue. The issue is that when I create a
base box, there's an additional NIC that's obtaining DHCP settings from
Using Centos 7.2 vm issuing a vagrant halt command is forcing a vm into
suspend mode and that only a virsh command can get the vm back anyone else
experience this effect and have a fix???
--
This mailing list is governed under the HashiCorp Community Guidelines -
bp8.txt as follows:
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure(2) do |config|
config.vm.box = "file://home/bob/vagrant/_box/8gb.box"
config.ssh.username = "bob"
config.ssh.password = "bobbob"
end
On Saturday, May 28, 2016 at 11:19:55 AM UTC-7, BRIT wrote:
>
> I've created
Also noticed that the config.vm.box was missing a "/" so it now reads as
config.vm.box ="file:///home/bob/vagrant/_box/8gb.box"
Unfortunately, I'm still getting the same error:
*Bringing machine 'default' up with 'virtualbox' provider...*
*There are errors in the configuration of this machine.
So perhaps this is something wrong with my (recently built) Ubuntu system,
but I can't add *any* public or private boxes from hashicorp.
cd ~/vagrant
mkdir ama
cd ama
vagrant init cbednarski/ubuntu-1404
vagrant up
[ error message : vm:
* The box 'cbednarski/ubuntu-1404' could not be found.
]
