StrongHorse8

1 Question, 4 Answers

Active since 10 January 2023

Last activity one year ago

Reputation

Badges 1

4 × Eureka!

Questions 1
Answers 4

0 Votes

10 Answers

975 Views

0 Votes 10 Answers 975 Views

Hi! I Am Setting Up A Few Clearml Agents To Run On A Local Gpu Server. They Have To Run In Their Own Docker Containers, Since We'Re Not Allowed To Install A Python Runtime On The Server Directly. I Got One Agent Running Listening To The Default Queue, Bu

Hi! I am setting up a few ClearML agents to run on a local GPU server. They have to run in their own Docker containers, since we're not allowed to install a ...

clearml

3 years ago

0 Hi! I Am Setting Up A Few Clearml Agents To Run On A Local Gpu Server. They Have To Run In Their Own Docker Containers, Since We'Re Not Allowed To Install A Python Runtime On The Server Directly. I Got One Agent Running Listening To The Default Queue, Bu

🤔 Hmm, yes, I suppose I can do that.

Ah, yes, I found the Dockerfile on the clearml-agent already. Should be doable!

Thanks for the suggestion!

3 years ago

Hi Alon,

Thanks! I know that already. I am more looking for a solution to spin up the Docker container automatically without having to manually log into each one of them and start a clearml-agent from there.

Sorry for the confusion.

3 years ago

Hi TimelyPenguin76

Both. The agent has to run inside a container and it will spin up sibling containers to run the tasks.

3 years ago

For future reference, there's actually an easier way.

The entrypoint of the Docker container accepts CLEARML_AGENT_EXTRA_ARGS. So adding CLEARML_AGENT_EXTRA_ARGS=--queue new_queue_name --create-queue to your environment let's it work with the default clearml-agent image.

Unfortunately, nowhere to be found in the documentation, but you can see it in the repository: https://github.com/allegroai/clearml-agent/blob/master/docker/agent/entrypoint.sh

3 years ago