SSH agent forwarding in orb machine - communication with agent failed

[fikovnik]

I created a new orb machine (Ubuntu 24.10).
I log into it using ssh orb.
The shell has environment variables:

SSH_AUTH_SOCK="/opt/orbstack-guest/run/host-ssh-agent.sock"
SSH_CONNECTION="::1 0 ::1 22"

but

ssh-add -l
error fetching identities: communication with agent failed

On the host ssh-add -l works fine.
I guess I misunderstood something, but what do I do wrong?

[WuHaiYanShan]

Me too. May I ask if you have solved it?

[MethorZ]

I have the same issue regarding the forwarding of the local Mac SSH agent into orbstacks VM, and therefore also containers.

I tried the local mac ssh agent as well as the homebrew version, both fail with the same error.

--
Additionally I found this in the logs

cat ~/.orbstack/log/vmgr.log | grep -i "ssh\|unix-nat"                                                                                                                                                                                                                                                               
🌲 vmgr | time="07-10 09:59:24" level=info msg="forwarding SSH agent" sock=none
🌲 vmgr | time="07-10 09:59:47" level=error msg="unix-nat forward: dial failed" addr=none error="dial unix none: connect: no such file or directory"
🌲 vmgr | time="07-10 10:00:21" level=error msg="unix-nat forward: dial failed" addr=none error="dial unix none: connect: no such file or directory"

I made sure multiple times that everything is working and set up correctly, ranging from local ssh agent, usage, launchctl, privileges, etc.

Is there a known issue or bug regarding this topic? Any hint on solving this would be awesome!

[MethorZ]

Allright - so for anyone that might encounter similar problems and has no idea what it could be.

I found out that, since Orbstack relies on the .ssh/config that overriding or using a wildcard statement like this, will cause this issue

Host *
    ...
    IdentityAgent none
    ...

Since the local socket will not be passed to the vm + therefore the containers.