Yes, looks like the solution, I've been working on it for the past 5min
Will let you know:)

Thanks a lot @<1523701070390366208:profile|CostlyOstrich36> ! Will take a look in a few hours.

Hi @<1717350332247314432:profile|WittySeal70> , you can simply change the service definition for the services agent in the server's docker compose so that the host's .ssh folder will be mapped into the services agent container, this should allow it to use the SSH key there to connect to GitHub

And here's when I've tried to test the connection within the agent's container

Hi @<1717350332247314432:profile|WittySeal70> , to address your questions:

• I think you can control it from here basically - None going through the route of the docker compose I found it - None . Regarding the image, I think you can use another image but the services agent is only for running pipeline controllers which are simply logic controllers.
• You might need to perform 2FA on the machine first

@<1523701087100473344:profile|SuccessfulKoala55> could you assist, please?

Hey, @<1523701087100473344:profile|SuccessfulKoala55> it works!) Thanks:)

Two more questions, if you will.

• For a regular worker I can specify python executable using agent.python_binary setting. How can I do in for a service worker? Should I tweak it inside the container as well?
• (kinda stupid question) Do you know if specifying agent.git_user & agent.git_pass using https works for github as it requires 2FA now?

Error I've got:

And one more thing that relates to the q#1 - is it safe to use more resent base image for agent-services service in docker compose? I see the specified latest tag point to image which was updated like 3 years ago..

Hi @<1717350332247314432:profile|WittySeal70> , are you using a self hosted server or the community?

Hi! Self hosted.