ZanySealion18 perhaps when you run with sudo for some reason the agent also sees SSH_AUTH_SOCK
in the env? If that env var is present, the agent will add it to the docker command and will map the SSH folder regardless of the configuration setting
Weird. When I spawn agent with sudo I get this behaviour. Without sudo everything works fine