Per default your SSH Key at
~/.ssh/id_rsa is added to the Docker containers from
If you need another key, read the documentation of
pygmy about this.
How it works¶
amazeeio/ssh-agentcontainer with a volume
pygmyadds a default SSH key from the host into this volume
docker-compose.ymlshould have volume inclusion specified for CLI container: ``` volumes_from:
- container:amazeeio-ssh-agent ```
- When CLI container starts, the volume is mounted and an entrypoint script adds SHH key into agent. @see https://github.com/amazeeio/lagoon/blob/master/images/php/cli/10-ssh-agent.sh
ssh-add -L within CLI container should show that the SSH key is correctly loaded.
SSH Key issues¶
As everything on amazee.io works with key authentication sometimes you might run into issues where the drush aliases aren't displayed or you can't connect to the servers.
Could not load API JWT Token, error was: 'email@example.com: Permission denied (publickey).'
Or for legacy systems:
firstname.lastname@example.org:~/public_html/docroot (staging)$ drush @master ssh Permission denied (publickey).
- Check if you see the SSH Key inside your container with
If you get
Could not open a connection to your authentication agent.or
The agent has no identities.head straight to step 3.
- Check if you see your SSH Key in
- If you don't see the key in
pygmy addkey. You should see
Successfully added ssh keyif the key addition was successful.
- After that you need to recreate the containers
docker-compose up -d --force
- When the containers are recreated you should be able to see your ssh key with
- If you still get the
Permission denied (publickey)error get in touch with our engineers to check if the key is configured correctly on the hosting side.