I am getting this exact error too.
The checksum for /tmp/composer-installer.php did not match e0012edf3e80b69788
49f5eff0d4b4e4c79ff1609dd1e613307e16318854d24ae64f26d17af3ef0bf7cfb710ca74755
a; it was 8a122319b9b85eb65da32aa900c77529d96b111fc56411ff4ae0b8769f3366898c9
6e8b1b276879cfe717eb161d85398.
fatal: [default]: FAILED! => {“changed”: true, “checksum_dest”: null, “checksum_src”: “5f4fdb96fd066d6e87bbe185d3e7b60fbaa039de”, “dest”: “/tmp/composer-installer.php”, “elapsed”: 0, “src”: “/root/.ansible/tmp/ansible-moduletmp-1592929919.3565352-vtqgckj1/tmp3ut5ap_h”, “url”: “https://getcomposer.org/installer”}
I performed a manual install on the VM using a simple apt-get install composer.
I commented out - { role: composer, tags: [composer] } in my dev.yml // the tags approach never worked for me https://roots.io/docs/trellis/master/local-development/
The documentation for Trellis is lacking in general it seems.
I then re-run the provision. However, I am given a similar problem with wp-cli (an issue with the gpg key).
non-zero return code
gpg: Signature made Tue 12 Nov 2019 06:03:46 PM UTC
gpg: using RSA key 63AF7AA15067C05616FDDD88A3A2E8F226F0BC06
gpg: issuer “releases@wp-cli.org”
gpg: directory ‘/root/.gnupg’ created
gpg: /root/.gnupg/trustdb.gpg: trustdb created
gpg: BAD signature from “WP-CLI Releases releases@wp-cli.org” [unknown]
fatal: [default]: FAILED! => {“changed”: false, “cmd”: [“gpg2”, “–lock-never”, “–no-default-keyring”, “–keyring”, “/tmp/wp-cli.pgp.gpg”, “–verify”, “/tmp/wp-cli-2.4.0.phar.asc”, “/tmp/wp-cli-2.4.0.phar”], “delta”: “0:00:00.070498”, “end”: “2020-06-23 16:40:29.930083”, “rc”: 1, “start”: “2020-06-23 16:40:29.859585”, “stderr_lines”: [“gpg: Signature made Tue 12 Nov 2019 06:03:46 PM UTC”, “gpg: using RSA key 63AF7AA15067C05616FDDD88A3A2E8F226F0BC06”, “gpg: issuer “releases@wp-cli.org””, “gpg: directory ‘/root/.gnupg’ created”, “gpg: /root/.gnupg/trustdb.gpg: trustdb created”, “gpg: BAD signature from “WP-CLI Releases releases@wp-cli.org” [unknown]”], “stdout”: “”, “stdout_lines”: []}
SO I log back into the vagrant VM and attempt a manual install of wp-cli. However, I am greeted with the exact same error.
Interestingly, if I download wp-cli outside the VM using the host OS and copy it to the VM then it works. For example, if I run
```
curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
in the trellis home directory using a wsl shell I can then access that file in the VM at /vagrant
I can then copy it to the vm’s home dir
cp ./wp-cli.phar ~
then
cd
chmod +x wp-cli.phar
sudo mv wp-cli.phar /usr/local/bin/wp
An it works.
So, I comment out { role: wp-cli, tags: [wp-cli] } in dev.yml and reprovision.
Then…
rsync: rename failed for “/srv/www/alexfordfitness.com/current/.env” (from
.~tmp~/.env): Operation not permitted (1)
rsync error: some files/attrs were not transferred (see previous errors)
(code 23) at main.c(1196) [sender=3.1.2]
failed: [default -> 127.0.0.1] (item=alexfordfitness.com) => {“ansible_loop_var”: “item”, “changed”: false, “cmd”: “/usr/bin/rsync --delay-updates -F --compress --checksum --archive --out-format=<>%i %n%L /tmp/alexfordfitness.com.env /srv/www/alexfordfitness.com/current/.env”, “item”: {“key”: “alexfordfitness.com”, “value”: {“admin_email”: “skywriter@gmail.com”, “cache”: {“enabled”: false}, “local_path”: “…/alexfordfitness.com”, “multisite”: {“enabled”: false}, “site_hosts”: [{“canonical”: “alexfordfitness.local”, “redirects”: [“www.alexfordfitness.local”]}], “ssl”: {“enabled”: false, “provider”: “self-signed”}}}, “rc”: 23}
So I delete the .env file from the offending directory and try again.
I’ll keep you up to date with my developments. I have other things to be getting on with atm.
