Describe the bug
Occasionally, when SSH-ing into the local CLI container the following error is returned and prevents the connection.
❯ docker-compose run --rm cli wp post update 132615 --post_status=draft;
ln: '/tmp/amazeeio_ssh-agent/socket' and '/tmp/amazeeio_ssh-agent/socket' are the same file
To Reproduce
Unclear, it just happens occasionally when using something like docker-compose run --rm cli sh
Describe the bug Occasionally, when SSH-ing into the local CLI container the following error is returned and prevents the connection.
To Reproduce Unclear, it just happens occasionally when using something like
docker-compose run --rm cli sh
Expected behavior The connection should happen.
Additional context Looking at https://github.com/amazeeio/lagoon/blob/f94b13eb91c1016aad7dc0360ff17e1f27aa4e6e/images/php/cli/10-ssh-agent.sh#L6-L7 it seems like the symlink still exists but is no socket anymore?
The current workaround is to run
docker exec -it amazeeio-ssh-agent rm -rf /tmp/amazeeio_ssh-agent/socket
and then run the previous command again.Pygmy Version: 0.9.10 macOS Version: 10.15.4 (19E266)