BTW: if you need to set env variables you can also add -e PYTHONPATH=/new/path to the docker args

Also what is the base path where the git repo is cloned? So if my repo is called myProject.git, what would the full path be?

👍

Woot woot!

Good question. The repo I'm using requires nvidia GPU and I can't get the code to run locally

Per my question above, what is the base path where the git repo is cloned?

Okay I will try the CLI thanks

Would that go under arguments ?

You will be able to set it.
You will just not see the output in the console log , but everything is running and being executed

Hey triggering the tasks from the CLI resolved the python pathing issues!

Would that go under

arguments

?

yes 🙂

Also what is the base path where the git repo is cloned? So if my repo is called myProject.git, what would the full path be?

For example https://github.com/ <user>/myProject.git
btw: how come you do not have this field auto populated from running the code locally or using clearml-task CLI?

First I would check the CLI command it will basically prefill it for you:
https://clear.ml/docs/latest/docs/apps/clearml_task
Specifically to your question, working directory "." is the root of the git repo
But I would avoid adding it manually, use the CLI, it will either use ask you to provide info or take the git repo details from the local copy

Hi BoredHedgehog47 , did you run in docker mode?

BoredHedgehog47 if you are running it on K8s, then the setup script is running before everything else, even before an agent appears on the machine, unfortunately this means the output is not logged yet, hence the missing console lines (I think the next version of the glue will fix that)
In order to test you can do:
export TEST_MEthen inside your code you will be able to see it
os.environ['TEST_ME']Make sense ?

yes makes sense. So I wouldnt be able to setup the PYTHONPATH via the setup script?