RESOLVED: Issue with Mutagen

[erikhansen]

I wanted to post this here in case anyone else runs into this same issue. I was getting this error when running warden env up (or more specifically warden sync start):

erikhansen@Eriks-MBP exampleproduct % warden env up
Creating network "exampleproduct_default" with the default driver
Creating exampleproduct_elasticsearch_1 ... done
Creating exampleproduct_rabbitmq_1      ... done
Creating exampleproduct_redis_1         ... done
Creating exampleproduct_db_1            ... done
Creating exampleproduct_php-fpm_1       ... done
Creating exampleproduct_php-debug_1     ... done
Creating exampleproduct_nginx_1         ... done
Connecting traefik to exampleproduct_default network
Connecting tunnel to exampleproduct_default network
Connecting mailhog to exampleproduct_default network
Starting exampleproduct_db_1            ... done
Starting exampleproduct_elasticsearch_1 ... done
Starting exampleproduct_rabbitmq_1      ... done
Starting exampleproduct_redis_1         ... done
Recreating exampleproduct_php-fpm_1     ... done
Recreating exampleproduct_nginx_1       ... done
Recreating exampleproduct_php-debug_1   ... done
Installing agent...                                                             
Error: unable to connect to beta: unable to connect to endpoint: unable to dial agent endpoint: unable to install agent: unable to invoke agent installation: exit status 1
ERROR: Command `mutagen sync create -c "${MUTAGEN_SYNC_FILE}" --label "warden-sync=${WARDEN_ENV_NAME}" --ignore "${WARDEN_SYNC_IGNORE:-}" "${WARDEN_ENV_PATH}${WARDEN_WEB_ROOT:-}" "docker://$(warden env ps -q php-fpm)/var/www/html"` at /opt/warden/commands/sync.cmd:45 failed with exit code 1

[erikhansen]

I was only getting this error on a client project. My Magento 2.4 demo site was syncing fine. After running the commands below on my Mac (not inside Warden), my problem was solved:

cd <PATH TO MAGENTO ROOT>
find ./ -type d -exec chmod 775 {} +
find ./ -type f -exec chmod 664 {} +

[erikhansen]

I thought the commands above are what fixed it, but I ran into the issue again and tried running those commands, to no avail. However I waited 10 minutes and ran warden sync start and then the sync worked just fine. Not sure what's the cause of that, but I'll report back if I find out anything more.

[drpayyne]

Thank you for this!

[erikhansen]

For the record, this is what I use to spin up new environments with as little manual intervention as possible:

warden svc up && warden env up; until warden sync start; do echo "trying again in 60 seconds..."; sleep 60; done; notify

What the result looks like:

notifier is a custom alias I have setup that pings a notification on my Mac using the terminal-notifier app:

alias notify="terminal-notifier -message 'Done'; say 'Done'"

[erikhansen]

For the record, it appears that this issue is no longer present on the latest version of Docker (Docker Desktop 4.10.0 (82025)) and this Warden fork.