I think 1. is described here: None

but I don't think there's a complete working example of how to achieve it in the docs

the host .ssh is empty, because all it has is the forwarded agent

it turns out the approach outlined in the issue 45 above works just fine, the problem was me not having the local keychain setup properly, sorry about that

so tl;dr: following None and just adding those two extra docker arguments indeed makes the whole pipeline `local ssh -> forward -A to server -> start an agent with extra docker args -> agent can correctly use l...

hi @<1523701205467926528:profile|AgitatedDove14> , thank you

• owning the agent helps, but still it's much better if the credentials don't show up in logs, console, files... I mean there's a reason ssh agent forwarding is preferred, it simply is more secure :)
• how does force_git_ssh_protocol help please? it doesn't solve the issue of the agent simply not having access

Apparently None should have fixed this exact issue, however, I'm unfortunately unable to reproduce it 😞