Feature or enhancement request details

At present, I can mount my host SSH_AUTH_SOCK into a container using a technique like this, so that I can do git clone using ssh:

container run --volume "${SSH_AUTH_SOCK}:/run/ssh-auth.sock" --env SSH_AUTH_SOCK=/run/ssh-auth.sock ...

This works fine as long as my login session lasts. If I logout, login, and container start the container, the auth forwarding doesn't work anymore because SSH_AUTH_SOCK points to a new location. Since the mount is defined in the container configuration, the mount becomes stale.

Adding a boolean --ssh flag (defaulting to false so that the user opts into the special behavior) would allow the system to specify the mount anew every time the container starts. It improves UX because the user no longer needs to remember the -v/-e dance, and it may help with delivering #421.

Code of Conduct

• I agree to follow this project's Code of Conduct