DevOps Community Sponsored by Cloud Posse

SweetOps

Hey, I'm trying to share my host's SSH agent with the container. Is that possible? AFAIK, when `SSH_AUTH_SOCK` is specified on the host, it should be shared with the container. I have the env variable exported, `.ssh` dir can be read in the container, etc. However, running `git pull` on any repo shows "Bad owner or permissions on /root/.ssh/config" error. Is there any log that shows sharing of the SSH agent was successful or any other indicator that it works?

&gt; AFAIK, when `SSH_AUTH_SOCK` is specified on the host, it should be shared with the container. I

This will not work across OS architectures (e.g. mac --&gt; linux)

Basically, it will only work if you're on linux

Maybe, it's the first time I try to use such thing :sweat_smile: Additionally, I use Rancher Desktop, not Docker Desktop and it may be not implemented there.

Is there anyone in your team that uses this functionality and could advise on that?

Yes, then socket bind mounting will not work;

Cannot bind a macOS socket into a virtual machine running linux :smiley:

Wait, what? <@UB2EH889X> Geodesic did this automatically for a long time. What changed?

> If the `SSH_AUTH_SOCK` environment variable is set on the host, it will be used by Docker, and the
> Docker container will have access to the host SSH agent. The host `$HOME/.ssh` directory will also
> be mounted automatically (unless you suppress it), so the container will have access to the host's SSH keys
> and configuration, giving you a choice of how to manage your SSH keys.
> 
> We recommend you use the host's security mechanisms to secure your SSH keys, and add them to the host's
> SSH agent to make them accessible to the container.
<@U07GN489UGG> Are you using Docker? Do you have file/directory ownership mapping working? <https://github.com/cloudposse/geodesic/issues/594|https://github.com/cloudposse/geodesic/issues/594> 

Yes, I run Geodesic (Debian Linux) on my Mac via Docker, and share the SSH agent. Don't you? 

Using atmos natively these days since we have the toolchain and auth support built in. 

<@UB90MG971>, sorry for late reply. Using Rancher Desktop - maybe that's the reason. I've seen some related issues in their GitHub.

Right, the SSH agent support is a Docker Desktop feature. I think OrbStack might have something similar, but AFAIK none of the other container engines have any special support for it. .