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! Can You Clarify, How We Can Support Following Scenario With Clearml. We Have Single Clearml Server With Multiple Workers In Docker Mode. We Also Have Multiple Teams. They Work On Different Projects Stored In Different Repositories(Public/Private Gi

Hello!
Can you clarify, how we can support following scenario with ClearML.
We have single ClearML server with multiple workers in docker mode. We also have multiple teams. They work on different projects stored in different repositories(public/private github/gitlab) with different credential/ssh keys.
As I understand ClearML has following features:

  1. Git credetials could be specified as parameter in ~/.clearml.conf or via command line of worker. We can specify only one user, but we have different users.
  2. SSH keys from host machine are mounted to ~/.ssh inside docker container. I don't know, how particular task could place ssh keys to host machine on startup.
    Can you help us with this case ?
  
  
Posted 2 years ago
Votes Newest

Answers 5


I think you'll have to do that inside the docker - you can use the custom bash script in order to do that (see https://github.com/allegroai/clearml-agent/blob/742cbf57670815a80a0c502ef61da12521e1e71f/docs/clearml.conf#L140 for a global agent setting, or you can do that specifically for a task using the execution container configuration)

  
  
Posted 2 years ago

So, did I understand you correctly? I create single ssh key and place it to ~/.ssh dir of all workers. After that anyone, who wants to run task on their repo, should add this key to their user in their repo.

  
  
Posted 2 years ago

Hi 🙂
Regarding #2 - the SSH keys for the host machines can simply be updated in GitLab/GitHub etc. so that each most machine (and so each docker executed on that machine that has the .ssh dir mounted inside it) can clone any of your repositories

  
  
Posted 2 years ago

Yeah, that's a possible solution 🙂

  
  
Posted 2 years ago

Thanks! This works for me except one thing. This work only with keys wit standard names. If keys have non-standard names should I deal with starting ssh-agent and ssh-add inside docker or there is simple way ?

  
  
Posted 2 years ago