Homestead: Composer update warning

[it-can]

Versions

• Vagrant: Vagrant 2.0.2
• Provider: VMWare Fusion 10
• Mac OS X High Sierra 10.13.3

I updated my Laravel Homestead box to laravel/homestead (vmware_desktop, 5.1.0)

When running vagrant reload --provision I noticed a error thrown by Composer.

==> homestead-7: Running provisioner: shell...
    homestead-7: Running: script: Update Composer
    homestead-7: You are running composer as "root", while "/home/vagrant/.composer" is owned by "vagrant"
    homestead-7: You are already using composer version 1.6.3 (stable channel).

[svpernova09]

This is nothing to worry about. This is the result of an upstream change to ensure .composer is owned by the vagrant user.

[antoclk]

i get this error too and won't let me run correctly my homestead.test

[islander]

Same here, provisioning not working:

==> homestead-7: Running provisioner: shell...
     homestead-7: Running: /tmp/vagrant-shell20180925-16933-bpwcx0.sh
==> homestead-7: Running provisioner: shell...
    homestead-7: Running: /tmp/vagrant-shell20180925-16933-w7699k.sh

After this code directory is empty and i need to make vagrant@homestead:~$ composer create-project --prefer-dist laravel/laravel code to get things done.

My setup:

Ubuntu 18.04.1
VirtualBox 5.2.10

My Homestead.yaml

---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox

authorize: ~/.ssh/id_ed25519.pub

keys:
    - ~/.ssh/id_ed25519

folders:
    - map: ~/code
    to: /home/vagrant/code

sites:
    - map: homestead.test
    to: /home/vagrant/code/public

databases:
    - homestead

UPD: I think, this is by design, there is no provisioning for bootstrapping laravel inside VM?