Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hello, I Am Trying To Run A Task In An Ec2 Worker With The Respective Agent In Docker Mode. I Am Using A Custom Docker Image. The Agent Is Configured To Use Ssh Authentication To Checkout The Code From Github (And It Does Check It Out In Pip/Poetry Mode)

Hello, I am trying to run a task in an EC2 worker with the respective agent in Docker mode. I am using a custom docker image.

The agent is configured to use SSH authentication to checkout the code from github (and it does check it out in pip/poetry mode). Now, I am running the agent in docker mode like this:

SSH_AUTH_SOCK=<file_socket> clearml-agent daemon --queue <your queue name>  --docker <custom docker image> 

as per None

But I get this error:

fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
error: Could not fetch origin

Any guidance to debug this issue would be greatly appreciated. Thanks.

  
  
Posted one year ago
Votes Newest

Answers 7


Update

I ran:

clearml-agent build --id <task-id> --docker <custom-docker> --log-level DEBUG --entry-point reuse_task

and got a similar problem:

Host key verification failed.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
error: Could not fetch origin
  
  
Posted one year ago

@<1603198134261911552:profile|ColossalReindeer77> if the issue is the host key verification, you can simply add the host to the known_hosts file on the instance before running the agent

  
  
Posted one year ago

Hey @<1523701087100473344:profile|SuccessfulKoala55> I am not sure this is the case as the instance can checkout code in poetry/pip mode. This issue only happens if I try to run the agent in docker mode. I read in the docs that when you run the agent in docker mode the . ssh directory of the host is copied to the container under /root/.ssh so I have the theory that when I am building the custom docker image I don’t end up with a /root folder (?) I haven’t had the time to debug this yet but if that is the case then this would explain why my container doesn’t have the credentials….

  
  
Posted one year ago

What I meant was that the host is not in known_hosts for the container - you can simply make sure it's injected there in the extra docker bash script configuration (in the agent configuration)

  
  
Posted one year ago

Hi @<1523701087100473344:profile|SuccessfulKoala55> thanks for your reply. Not sure where I can find more about the extra docker bash script that you mention… I would appreciate if you can point me in the right direction. Thanks.

  
  
Posted one year ago

Hi @<1603198134261911552:profile|ColossalReindeer77> , see here: None

  
  
Posted one year ago

Also @<1619867994005966848:profile|HungryTurtle13> 👆

  
  
Posted one year ago