tomjn
commented
2 years ago The relevant log parts from the log file don't give much information, just that it finished Apt package handling, proceeded on then reached NVM, saw it was installed, and failed:
php5.6-imagick php5.6-memcache php5.6-memcached php5.6-msgpack php5.6-ssh2
php5.6-xdebug php7.0-igbinary php7.0-imagick php7.0-memcache
php7.0-memcached php7.0-msgpack php7.0-ssh2 php7.0-xdebug php7.1-igbinary
php7.1-imagick php7.1-memcache php7.1-memcached php7.1-msgpack php7.1-pcov
php7.1-ssh2 php7.1-xdebug php7.2-igbinary php7.2-imagick php7.2-memcache
php7.2-memcached php7.2-msgpack php7.2-pcov php7.2-ssh2 php7.2-xdebug
php7.2-yaml php7.3-igbinary php7.3-imagick php7.3-memcache php7.3-memcached
php7.3-msgpack php7.3-pcov php7.3-ssh2 php7.3-xdebug php7.3-yaml
php7.4-igbinary php7.4-imagick php7.4-memcache php7.4-memcached
php7.4-msgpack php7.4-pcov php7.4-ssh2 php7.4-xdebug php7.4-yaml
php8.0-igbinary php8.0-imagick php8.0-memcache php8.0-memcached
php8.0-msgpack php8.0-pcov php8.0-ssh2 php8.0-xdebug php8.0-yaml snapd
sosreport ubuntu-advantage-tools ubuntu-server
0 upgraded, 0 newly installed, 0 to remove and 81 not upgraded.
[0m[39m[2m * Registering apt packages to install[21m[0m
[0m[39m[2m ▷ Running [0m[1m[0;38;5;5mregister_apt_packages[21m[0m[39m[2m hook[21m[0m
[0;38;5;2m ✔ Finished [0m[1m[0;38;5;5mregister_apt_packages[21m[0;38;5;2m hook in [0m[0m[1m[0;38;5;5m1s[21m[0m[0m
[0m[39m[2m * Main packages check and install.[21m[0m
[0m[39m[2m * Checking for apt packages to remove.[21m[0m
[0m[39m[2m * No apt packages to remove[21m[0m
[0m[39m[2m * Checking for apt packages to install.[21m[0m
[0m[39m[2m * No apt packages to install[21m[0m
[0m[39m[2m * Running after_packages[21m[0m
[0m[39m[2m ▷ Running [0m[1m[0;38;5;5mafter_packages[21m[0m[39m[2m hook[21m[0m
false
[0m[39m[2m * Adding Mailhog service file[21m[0m
[0m[39m[2m * Enabling MailHog Service[21m[0m
[0m[39m[2m * Starting MailHog Service[21m[0m
[0m[39m[2m * Checking for NVM[21m[0m
[0;38;5;2m ✓ NVM is already installed, checking for updates[0m[0m
HEAD is now at 9600617 v0.39.1
/home/vagrant
[0m[39m[2m - Loading nvm[21m[0m
[0;38;5;9m ! The [0m[1m[0;38;5;5m'main'[21m[0;38;5;9m provisioner ran into problems, the full log is available at [0m[1m[0;38;5;5m'/var/log/provisioners/2022.06.13_16-40-42/provisioner-main.log'[21m[0;38;5;9m. It completed in [0m[1m[0;38;5;5m20[21m[0;38;5;9m seconds.[0m[0m
While reprovisioning an old VVV that had the nvm extension, I upgraded to 3.10
develop, and reprovisioned, but it kept failing at the NVM stageIn the end, removing the NVM extension and using what came with VVV, combined with a
vagrant sshand arm -rf ~/.nvmresolved the issue ( though I ran into other unrelated problems ).Given that the nvm extesion got rewritten and merged, I'm not so fussed on fixing it up, though a VVV version check may be useful.
I do think VVV core should be able to detect when this situation has happened and fix it though.