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
Hi, I Want To Pass Environment Variables From The Host To The Docker Containers Running My Task. I Managed To Use

Hi, I want to pass environment variables from the host to the docker containers running my task. I managed to use extra_docker_shell_script: ["export SECRET=SECRET", ] to make the secret environment variable available. Unfortunately I was not able to pass the environment variable from the host the same way using SECRET=$SECRET or SECRET=${SECRET}. What would be the right way to pass the environment variable?

  
  
Posted 3 years ago
Votes Newest

Answers 7


but is there any other way to get env vars / any value or secret from the host to the docker of a task?

if this is docker -e/--env as argument would do the same
-e VAR=somevalue

  
  
Posted 3 years ago

but this would be still part of the clearml.conf right?

You can pass it per Task , also you can configure the agent to always pass it add this env.
https://github.com/allegroai/clearml-agent/blob/5a080798cb4292e198948fbe16cba70136cb6bdf/docs/clearml.conf#L137

  
  
Posted 3 years ago

I like this approach more but it still requires resolved environment variables inside the clearml.conf

  
  
Posted 3 years ago

I can figure out a way to resolve it, but is there any other way to get env vars / any value or secret from the host to the docker of a task?

  
  
Posted 3 years ago

I like this approach more but it still requires resolved environment variables inside the clearml.conf

Yes 😞 maybe this is a feature request ?

  
  
Posted 3 years ago

but this would be still part of the clearml.conf right? I would prefer a way around clearml.conf to avoid resolving the variables

  
  
Posted 3 years ago

Hi ClumsyElephant70

extra_docker_shell_script: ["export SECRET=SECRET", ]

I think ${SECRET} will not get resolved you have to specifically have text value there.
That said it is a good idea to resolve it if possible, wdyt?

  
  
Posted 3 years ago
1K Views
7 Answers
3 years ago
one year ago
Tags
Similar posts