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
Hey All. I Need Some Help Debugging Some Errors. I Keep Getting An Error About Failing To Clone The Repository On The Remote Instance. What Could Be The Reason Of This? Are There Any Common Errors Related To This? I Suspect Permissions, But Not Entirely

Hey all. I need some help debugging some errors.

I keep getting an error about failing to clone the repository on the remote instance. What could be the reason of this? Are there any common errors related to this? I suspect permissions, but not entirely sure what and where

  
  
Posted 3 years ago
Votes Newest

Answers 11


Hey @<1523701205467926528:profile|AgitatedDove14> I am helping Max to get this working. I ran the clearml-agent init and now have the correct entries in the clearml.conf file.

Created an ssh key from the agent, uploaded it to the git repo, but still getting this 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.

If I manually ssh on to the agent, and run:
git clone git@github.com:<repo_path> it clones just fine, so that rules out any connectivity issues.

Is there anything specific in the conf file I should look at?
Is there anyway to debug this from the docker container?

  
  
Posted 3 years ago

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

Just by chance I set the SSH deploy keys to write access and now we're able to clone the repo. Why would the SSH key need write access to the repo to be able to clone?

  
  
Posted 3 years ago

Sure, run:
clearml-agent initIt is a CLI wizard to configure the initial configuration file.

  
  
Posted 3 years ago

Hi @<1687643893996195840:profile|RoundCat60> , I just saw the message,

Just by chance I set the SSH deploy keys to write access and now we're able to clone the repo. Why would the SSH key need write access to the repo to be able to clone?

Let me explain, the default use case for the agent is to use user/pass (as configured in the clearml.conf file(
It will change any ssh links to https links and will add the credentials to clone the repository.
You can also provide SSH keys (basically whatever you have on the host machine will be used by the agent)
In that case, you should make sure it changes all the repo link to ssh links, by setting:
force_git_ssh_protocol: true
None

  
  
Posted 3 years ago

Is there any documentation on how to set up the config for the agent?

  
  
Posted 3 years ago

That is a bit odd, But SSH keys have to have a specific chmod flags for them to work (security issues)
What was the error ?

  
  
Posted 3 years ago

Yep i've done all that, it didn't seem to work until I set the deploy key to write

  
  
Posted 3 years ago

I am struggling to fill in the values for the template. Some are obvious, others are not

  
  
Posted 3 years ago

Thanks Martin. I think I have found where the error is!

  
  
Posted 3 years ago
1K Views
11 Answers
3 years ago
7 months ago
Tags