Failure to launch Homestead Vagrant Box

Question

I am in the middle of following Laravel Tutorial which directs me to installing the homestead vagrant box; I am stuck on composer part.

I use Ubuntu 14.04 LTS (64bit) and ran Vagrant through virtualbox 5.0.24r108355 (amd64). Apparently Homestead has conflict with virtualbox 5.1.

My understanding of Homestead is that it will set up

Ubuntu 16.04
Git
PHP 7.0
HHVM
Nginx
MySQL
MariaDB
Sqlite3
Postgres
Composer
Node (With PM2, Bower, Grunt, and Gulp)
Redis
Memcached
Beanstalkd

This is partly confirmed by the following: 16.04 LTS installation.

yhk@home:~/Homestead$ vagrant ssh
Welcome to Ubuntu 16.04 LTS (GNU/Linux 4.4.0-22-generic x86_64)
* Documentation:  https://help.ubuntu.com/
Last login: Fri Jul 15 13:20:08 2016 from 10.0.2.2

However, when I try vagrant up , it fails. Apparently, I am already using composer. How do I proceed along to fix this glitch and have vagrant up and running properly?

yhk@home:~/Homestead$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'laravel/homestead' is up to date...
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: flag to force provisioning. Provisioners marked to run always will still run.
yhk@home:~/Homestead$ vagrant provision
==> default: Running provisioner: file...
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: Running provisioner: shell...
    default: Running: /tmp/vagrant-shell20160715-14549-1a6hi0t.sh
==> default: Running provisioner: shell...
    default: Running: script: Creating Site: homestead.app
==> default: Running provisioner: shell...
    default: Running: script: Restarting Nginx
==> default: Running provisioner: shell...
    default: Running: script: Creating MySQL Database
==> default: Running provisioner: shell...
    default: Running: script: Creating Postgres Database
==> default: Running provisioner: shell...
    default: Running: script: Clear Variables
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: You are already using composer version 1.1.3 (stable channel).
==> default: Running provisioner: shell...
    default: Running: /tmp/vagrant-shell20160715-14549-l87w5y.sh

I think the setup properly done...

yhk@home:~/Homestead$ ls
CHANGELOG.md   composer.lock  init.bat  LICENSE.txt  scripts  Vagrantfile
composer.json  homestead      init.sh   readme.md    src

yhk@home:~/.homestead$ ls
after.sh  aliases  Homestead.yaml  Homestead.yaml~

Once again, how do I proceed along to get composer issue fixed and have vagrant up and running?

Answer 1

have you tried to run vagrant up with sudo privileges? cd to Homestead folder and execute

sudo vagrant up

and then see if the error remains. sometimes this is a issue related with permissions.