-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Cannot "ssh-add" since version 1.3 #10
Comments
@mbrodala Looks like you are using this image outside of it's primary intended use case - with Docksal - which is exciting! Mind sharing some details? :)
Here's why: That line moved in the entrypoint script of the image and is now executed unconditionally. You'd have to override the container ENTRYPOINT in the
|
I didn't even know Docksal is a thing. ;-) We only use this for a basic local development setup, so basically something like Docksal. ;-)
Thanks, I'll try that. However I think it would be a good idea to move the socket file cleanup right before the |
@mbrodala agreed. Released a hotfix v1.3.1. |
Hm, for some reason the issue remains with version 1.3. And there is no tag for 1.3.1. |
@mbrodala did you do |
Yes, I tried that version but without any change. Here's the current state locally:
Now that I saw that the ID is outdated I ran
And now I can use version 1.3 just fine. 👍 |
We are using the following service setup in our
docker-compose.yml
:While this works perfectly fine it fails since version 1.3 of this image.
With version 1.2:
With version 1.3:
The
/.ssh-agent
directory in thessh-agent
service looks fine if just that service is (re)started:However, as soon as the
ssh-key
service is executed, the socket files in this directory disappear. The logs ofssh-agent
do not show anything useful:Any idea what's going on? For now we need to stick with version 1.2.
The text was updated successfully, but these errors were encountered: