Roots Discourse

Vagrant Up Stuck on 'extracting composer'

#1

Hello,

I’m currently working on upgrading Trellis and have encountered a few issues along the way which I’m struggling to solve after exhausting this forum, and the rests of the topics Google finds.

Environment:

  • Mac OSX 10.13.4 (HighSierra)
  • Ansible 2.4
  • Vagrant 2.2.0
  • Composor 1.6.3
  • Virtualbox 5.2.26
  • Trellis 1.0.2

I’m upgrading Trellis from 0.9.8 to the current release of 1.0.2 for which I’ve performed the following:

  1. Updating Vagrant and Ansible to the versions mentioned above

  2. Pulled down the current version of Trellis via a Git remote into my working directory

  3. Vagrant destroy on the original VM (to get a clean slate).

  4. Run vagrant up

Now when running vagrant up it gets to the part where it begins running ansible-galaxy and downloading the Composer role but then just continually says extracting composer. It appears it’s either hitting an error or stuck in a loop as this will go on forever until exited manually. Running in debug mode doesn’t seem to provide any better information.

==> default: Checking for bindfs in VM...
    default: Package manager detected: apt-get
    default: Fuse kernel module is installed
    default: Fuse kernel module is loaded
    default: Bindfs 1.13.7 is installed
==> default: Machine is ready to use bindfs!
==> default: Creating bind mounts after synced_folders...
    default: /vagrant-nfs-premium.trendwatching.com => /srv/www/premium.trendwatching.com/current
    default: /ansible-nfs => /home/vagrant/trellis
    default: /home/vagrant/trellis/bin => /home/vagrant/trellis/bin
==> default: Running provisioner: ansible...
    default: Running ansible-galaxy...
- downloading role 'composer', owned by geerlingguy
- downloading role from https://github.com/geerlingguy/ansible-role-composer/archive/1.7.0.tar.gz
- extracting composer to /Trendwatching/Premium/trellis/vendor/roles/composer
- extracting composer to /Trendwatching/Premium/trellis/vendor/roles/composer
- extracting composer to /Trendwatching/Premium/trellis/vendor/roles/composer
- extracting composer to /Trendwatching/Premium/trellis/vendor/roles/composer
- extracting composer to /Trendwatching/Premium/trellis/vendor/roles/composer
- extracting composer to /Trendwatching/Premium/trellis/vendor/roles/composer
- extracting composer to /Trendwatching/Premium/trellis/vendor/roles/composer
- extracting composer to /Trendwatching/Premium/trellis/vendor/roles/composer
- extracting composer to /Trendwatching/Premium/trellis/vendor/roles/composer
- extracting composer to /Trendwatching/Premium/trellis/vendor/roles/composer
- extracting composer to /Trendwatching/Premium/trellis/vendor/roles/composer
- extracting composer to /Trendwatching/Premium/trellis/vendor/roles/composer
- extracting composer to /Trendwatching/Premium/trellis/vendor/roles/compose
... goes on like this with no end in site.

Has anyone encountered this before? Really not sure how to resolve this as the VM doesn’t seem to ever provision.

0 Likes