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
I Have A Docker Container That Have Clearml-Agent Running Inside In Normal Mode. The Agent Take On A Task And Execute It Fine. I Just Want To Somehow Log The Docker Image Version That The Agent Is Running Inside. I Start My Container With Something Like:

I have a docker container that have clearml-agent running inside in normal mode.
The agent take on a task and execute it fine.
I just want to somehow log the docker image version that the agent is running inside.
I start my container with something like:
docker run --rm -it agent-image /root/launch_agent.sh
Where launch_agent.sh basically call clearml-agent daemon
I saw that in docker mode, the "parent" agent start the docker container with -l foo=bar Is there a way that I can pass on the version with -l <what>=agent-image:v2 and the agent log that ?
Or may be via a environment variable -e <WHAT>=agent-image:v2 ?
@<1523701087100473344:profile|SuccessfulKoala55> @<1523701070390366208:profile|CostlyOstrich36>

  
  
Posted one year ago
Votes Newest

Answers 5


@<1523701087100473344:profile|SuccessfulKoala55> It's working !! Thank you very much !!! Clearml is awesome !!!!
image

  
  
Posted one year ago

you mean this dump section ?
image

  
  
Posted one year ago

@<1576381444509405184:profile|ManiacalLizard2> the agent basically logs the configuration but this is unrelated to the docker environment. You can theoretically simply add some custom name/value to the agent configuration an it should appear in the configuration dump printed by the agent

  
  
Posted one year ago

from what I understand, the docker mode were designed for apt based image and also running as root inside the container.
We have container that are not apt based and running not as root
We also do some "start up" that fetch credentials from Key Vault prior running the agent

  
  
Posted one year ago

Hi @<1576381444509405184:profile|ManiacalLizard2> , is there a specific reason you're running the agent inside a docker container instead of running the agent in docker mode which would make it spin up a container?

  
  
Posted one year ago
920 Views
5 Answers
one year ago
one year ago
Tags
Similar posts