4 ms·
If somebody needs a Vagrantfile for testing: https://gist.github.com/therealmarv/555f7efc1c55ffa288bca09191e4e705 https://gist.github.com/therealmarv/555f7efc1c
by therealmarv 11y ago
If somebody needs a Vagrantfile for testing: https://gist.github.com/therealmarv/555f7efc1c55ffa288bca09191e4e705 https://gist.github.com/therealmarv/555f7efc1c55ffa288bca091...
but it seems even Ubuntus Server are not speedy today (Atlas server are also slow)
(Update) it seems I'm getting an error with it :/
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'gurumeditation' state. Please verify everything is configured
properly and try again.
If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.
The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.
- matt4077 11y agoSomeone else in this thread posted something rather nonsensical about switching to Commodore 64. I was just about to make a guru meditation joke when I saw that someone apparently beat me to it. I'm running 16.04 with the Vagrant/Virtualbox image from atlas. I've tried getting it to work in the google cloud but had no luck there so far (it's possibly just the ssh key injection that failed, haven't had time to investigate).
- alyandon 11y agoIf you've recently upgraded to VirtualBox 5.0.18 you might try downgrading to 5.0.16 as I had a similar issue earlier this week.
- therealmarv 11y agoI've updated to the VirtualBox 5.0.19 test build which also fixes that. Bad timing for Ubuntu: https://www.virtualbox.org/wiki/Testbuilds https://www.virtualbox.org/wiki/Testbuilds