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 local git credentials work 🙂

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

owning the agent helps, but still it's much better if the credentials don't show up in logs,

They are not, they are always filtered out,

• how does force_git_ssh_protocol help please? it doesn't solve the issue of the agent simply not having accessIt automatically maps the host .ssh into the container, so that git can use SSH to clone.
  What exactly is not working?
  and how are you configuring it?

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

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

Hi @<1573119962950668288:profile|ObliviousSealion5>

Hello, I don't really like the idea of providing my own github credentials to the ClearML agent. We have a local ClearML deployment.

if you own the agent, that should not be an issue,, no?

forward my SSH credentials using

ssh -A

and then starting the clearml agent?

When you are running the agent and you force git clonening with SSH, it will autmatically map the .ssh into the container for the git to use

Basically just set the following and you should be fine
None