ClearML FAQ

Answered

🚨 Issue with Cloning ClearML Experiments Using SSH 🚨

Hey,

I've run into an issue while trying to clone a ClearML experiment that's configured with an SSH Git repository. The experiment is linked to a repository at git@gitlab-ssh.[our-company-domain].com:testgroup/testproject.git . However, when the ClearML agent tries to clone the repository, it fails with the following error:

Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

Context:

Agent Configuration:
I've configured the agent with the necessary settings to connect to Git:- git_host = "[our-company-domain].com"
git_user and git_pass are correctly set.
force_git_ssh_protocol = false- Despite these configurations, the SSH cloning still fails.
What I've Tried:
Draft Mode:
When I attempted to clone the experiment in Draft mode , I switched the repository URL from SSH to HTTPS ( https://[our-company-domain].com/gitlab/testgroup/testproject.git ). The cloning process worked successfully in this case.
Request for Help:
How can we ensure that HTTPs cloning works properly with the ClearML agent when clonin experiments?
Is there any CLEARML_GIT_REMOTE_URL env?
Any insights or suggestions would be greatly appreciated!
Thanks in advance for your help!

  				
Posted 
	4 months ago

					More
				  		
  Report
		
					ManiacalParrot65
				
					0
					 × 1

Votes Newest

Answers 7

the config as you show will try to use https connection in the first place, you have to remove user/pass for it to use ssh as far as I understand

  				
Posted 
	4 months ago

					More
				  		
  Report
		
					WittySeal70
				
					0
					 × 1

I actually want to use HTTPS instead of SSH, which is why I have set a username and password. However, the issue is that when I clone the repository, the link appears as git@gitlab-ssh.[our-company-domain].com:testgroup/testproject.git instead of https://[our-company-domain].com/gitlab/testgroup/testproject.git .

  				
Posted 
	4 months ago

					More
				  		
  Report
		
					ManiacalParrot65
				
					0
					 × 1

I found it easier to use HTTPS(:
When I manually changed the REPOSITORY prop in the cloned task from an ssh address to an https address, it worked fine. But I don't want to change the REPOSITORY every time I clone.

  				
Posted 
	4 months ago

					More
				  		
  Report
		
					ManiacalParrot65
				
					0
					 × 1

like so:

  				
Posted 
	4 months ago

					More
				  		
  Report
		
					WittySeal70
				
					0
					 × 1

hello , i've got exactly same issue recently. first I would advice you to check if you can connect to ssh within the docker container (if it runs in docker) or from your host.

try
ssh -T git@gitlab.com
does it connect?

  				
Posted 
	4 months ago

					More
				  		
  Report
		
					WittySeal70
				
					0
					 × 1

Hi @<1669152726245707776:profile|ManiacalParrot65> , if you configure the agent with agent.translate_ssh: true and provide agent.git_user and agent.git_pass it should translate the git SSH URL to HTTPS

  				
Posted 
	4 months ago

					More
				  		
  Report
		
					SuccessfulKoala55
				
					0
					 × 1

Funny, because when I faced the issue I thought it would be easier to use ssh and not user/pass (because gitgub uses 2FA and I was not sure (still not) how ClearML works with it).

What if you'd try manually change REPOSITORY prop in cloned task from ssh style address to https style?

  				
Posted 
	4 months ago

					More
				  		
  Report
		
					WittySeal70
				
					0
					 × 1

Write your answer

266 Views

7 Answers

4 months ago