Skip to content
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

devcontainer up: forward agent: dial unix /run/user/1000/keyring/ssh: connect: no such file or directory #1367

Open
ccl1115 opened this issue Nov 11, 2024 · 1 comment

Comments

@ccl1115
Copy link

ccl1115 commented Nov 11, 2024

What happened?
Get an error when start a workspace

[02:38:01] info Run command : yarn install...
[02:38:02] info yarn install v1.22.19
[02:38:02] info [1/4] Resolving packages...
[02:38:02] info [2/4] Fetching packages...
[02:38:05] info [3/4] Linking dependencies...
[02:38:06] info [4/4] Building fresh packages...
[02:38:06] info Done in 4.59s.
[02:38:07] info Successfully ran command : yarn install
[02:38:07] info Install extensions 'dbaeumer.vscode-eslint,streetsidesoftware.code-spell-checker' in the background
[02:38:07] info devcontainer up: forward agent: dial unix /run/user/1000/keyring/ssh: connect: no such file or directory
[02:38:07] error Try enabling Debug mode under Settings to see a more verbose output
[02:38:07] fatal run agent command: Process exited with status 1

I use kubectl exec to login into the pod, and seems there is no file under /run/user/1000/keyring/ssh, but seems the pod runs without no error.
I also try to set agent forwarding to false in the default context

devpod context set-options --context default --option SSH_AGENT_FORWARDING=false

But no luck for me.

What did you expect to happen instead?

How can we reproduce the bug? (as minimally and precisely as possible)

My devcontainer.json:
Just use the example project

Local Environment:

  • DevPod Version: v0.5.22
  • Operating System: mac
  • ARCH of the OS: ARM64

DevPod Provider:

  • Kubernetes Provider:
Client Version: v1.26.1
Kustomize Version: v4.5.7
Server Version: v1.25.5+k3s2

Anything else we need to know?

@bkneis
Copy link
Contributor

bkneis commented Nov 14, 2024

Thanks for reporting your issue @ccl1115! Can you please provide your up command your using? I noticed in the code that when specyfing either dot files, a git SSH signature via command arg or gpg forwarding the SSH_AUTH_SOCK is proxied

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants