vagrant develop branch provision output

vagrant develop branch provision output

Debbies-MBP:vagrant-local labedzde$ rm vvv-custom.yml
Debbies-MBP:vagrant-local labedzde$ git checkout develop
Branch develop set up to track remote branch develop from origin.
Switched to a new branch 'develop'
Debbies-MBP:vagrant-local labedzde$ vagrant up --provision
__ __ __ __
\ V\ V\ V / Varying Vagrant Vagrants
 \_/\_/\_/  v2.5.2-git::develop

Platform:   platform-darwin13.4.0 shell:/bin/bash vagrant-hostsupdater 
Vagrant:    2.2.4
VirtualBox: 6.0.4r128413

Docs:       https://varyingvagrantvagrants.org/
Contribute: https://github.com/varying-vagrant-vagrants/vvv
Dashboard:  http://vvv.test

Copying vvv-config.yml to vvv-custom.yml
IMPORTANT NOTE: Make all modifications to vvv-custom.yml in future so that they are not lost when VVV updates.

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/trusty64' version '20190315.0.0' is up to date...
==> default: [vagrant-hostsupdater] Checking for host entries
==> default: [vagrant-hostsupdater]   found entry for: 192.168.50.4 vvv
==> default: [vagrant-hostsupdater]   found entry for: 192.168.50.4 vvv.dev
==> default: [vagrant-hostsupdater]   found entry for: 192.168.50.4 vvv.test
==> default: [vagrant-hostsupdater]   found entry for: 192.168.50.4 vvv.local
==> default: [vagrant-hostsupdater]   found entry for: 192.168.50.4 vvv.localhost
==> default: [vagrant-hostsupdater]   found entry for: 192.168.50.4 one.wordpress.test
==> default: [vagrant-hostsupdater]   found entry for: 192.168.50.4 two.wordpress.test
==> default: Running provisioner: fix-no-tty (shell)...
The SSH connection was unexpectedly closed by the remote end. This
usually indicates that SSH within the guest machine was unable to
properly start up. Please boot the VM in GUI mode to check whether
it is booting properly.