-
-
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
Ssh-agent 1.4: Error connecting to agent from CLI #21
Comments
Can confirm I am getting the same error, however when I run
when using 1.4. By downgrading to 1.3 I'm able to use the commands as expected. I'll look into this a little further. |
On inspection, it would appear that the ENV variables are not getting set correctly. My 1.3 json has this: "Env": [
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"SSH_DIR=/.ssh",
"SOCKET_DIR=/.ssh-agent",
"SSH_AUTH_SOCK=/.ssh-agent/socket",
"SSH_AUTH_PROXY_SOCK=/.ssh-agent/proxy-socket"
], Where my 1.4 json has this: "Env": [
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"SSH_DIR=/.ssh",
"SOCKET_DIR=/.ssh-agent",
"SSH_AUTH_SOCK=/socket",
"SSH_AUTH_PROXY_SOCK=/proxy-socket"
], I'll create a PR that reverts the change to the Dockerfile that changes the way the env variables are set. |
@botanic You can get the latest version with the fix by running Thank you for reporting this. |
A hotfix has been just released. To get it right away:
|
When using 1.4 version, CLI container does not have access to ssh-agent.
On 1.4 this is what I see:
When I switch ssh-agent image to 1.3 everything works fine
I am using mac with M1 chip.
The text was updated successfully, but these errors were encountered: