-
Notifications
You must be signed in to change notification settings - Fork 293
dockerSsh option fails to mount non-RSA keys into container #488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
jacksgt
added a commit
to jacksgt/serverless-python-requirements
that referenced
this issue
Mar 9, 2020
This enables the user to use an key file format (RSA, ED25519, ...). Additionally, it allows more complex workflows (such as different SSH keys for specfic sites, such as Github or Bitbucket), since the .ssh/config file is also mounted into the container. Fixes serverless#488
jacksgt
added a commit
to jacksgt/serverless-python-requirements
that referenced
this issue
Mar 9, 2020
This enables the user to use an key file format (RSA, ED25519, ...). Additionally, it allows more complex workflows (such as different SSH keys for specfic sites, such as Github or Bitbucket), since the .ssh/config file is also mounted into the container. Fixes serverless#488
jacksgt
added a commit
to jacksgt/serverless-python-requirements
that referenced
this issue
Mar 9, 2020
This enables the user to use an key file format (RSA, ED25519, ...). Additionally, it allows more complex workflows (such as different SSH keys for specfic sites, such as Github or Bitbucket), since the .ssh/config file is also mounted into the container. Fixes serverless#488
jacksgt
added a commit
to jacksgt/serverless-python-requirements
that referenced
this issue
Mar 30, 2020
This enables the user to use an key file format (RSA, ED25519, ...). Additionally, it allows more complex workflows (such as different SSH keys for specfic sites, such as Github or Bitbucket), since the .ssh/config file is also mounted into the container. Fixes serverless#488
jacksgt
added a commit
to jacksgt/serverless-python-requirements
that referenced
this issue
Apr 23, 2020
This enables the user to use an key file format (RSA, ED25519, ...). Additionally, it allows more complex workflows (such as different SSH keys for specfic sites, such as Github or Bitbucket), since the .ssh/config file is also mounted into the container. Fixes serverless#488
jacksgt
added a commit
to jacksgt/serverless-python-requirements
that referenced
this issue
Sep 20, 2020
This enables the user to use an key file format (RSA, ED25519, ...). Additionally, it allows more complex workflows (such as different SSH keys for specfic sites, such as Github or Bitbucket), since the .ssh/config file is also mounted into the container. Fixes serverless#488
Here is a work around if you need to use a private repo:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per the README, "The dockerSsh option will mount your $HOME/.ssh/id_rsa and $HOME/.ssh/known_hosts as a volume in the docker container".
However, also other paths and key formats are used for SSH keys (e.g. specific SSH keys for specific sites, ecdsa or ed25510, etc.).
If no RSA SSH key is present, I get the following error:
Even if no RSA key is present, the plugin still tries to mount ~/.ssh/id_rsa into the container.
Docker then subsequently creates this path (as a directory), but with standard permissions (hence the above error message).
In the end, the SSH private key (which is in ~/.ssh/id_ed25519) is not present in the container, thus the "permission denied" error for the private repository occurs.
The text was updated successfully, but these errors were encountered: