Being able to create and remove queues as well as list their contents.

I do expect it to pip install though which doesn’t root access I think

I’ll try that!

The private_package can be installed by doing pip install git+ssh://git@github.com/user/private_package.git but the agent is trying to do pip install private_package which won’t work.

Ok!

AgitatedDove14 can I specify a script to be run after pip install packages is done? I see that it’s possible in docker mode.

Well this doesn’t work
pip install -e

Is there a way to make it use ssh+git instead of git+git ? Maybe add a force_ssh_pip_install to the agent config?

I hadn’t enabled that line when the failure happened.

Our code is tightly integrated with protobuffers which needs to be re-compiled every now and then. We have a script to do that. If that’s not done, some imports end up failing.

I think it works, I’m fixing something else that came up.

The commit is valid for sure.

btw, AgitatedDove14 I launch the agent daemon outside docker (with --docker ) , that’s the way it is supposed to work right?

$ clearml-agent daemon --detached --queue manual_jobs automated_jobs --docker --gpus 0
And then the worker itself will run the docker run command for me and start another non-daemon agent inside.
I guess the failure happens when it tries to switch to docker because the same experiment works with agents not started with --docker flag

I think it’s great to let users build their own UI-connected apps, I’d use that for sure!

If you were to add this, where would you put it? I can use a modified version of clearml-agent

Great find! So a pip upgrade should fix it hopefully.

AgitatedDove14 this works: pip install git+ssh://git@github.com/user/repo.git

It is indeed autopopulated by init

Issue seems fixed now, thanks! Is the fact that clearml-agent needs to be installed from system python mentioned anywhere in the docs, if not I suggest it gets added.

Thank you so much for helping.

OH! I was installing it on an env

$ python --version Python 3.6.8 $ python repo/toy_workflow.py --logtostderr --logtoclearml --clearml_queue=ada_manual_jobs 2021-08-07 04:04:16,844 - clearml - WARNING - Switching to remote execution, output log page https://...
On the webpage logs I see this:
2021-08-07 04:04:12 ClearML Task: created new task id=f1092bcbe30249639122a49a9b3f9145 ClearML results page: `
2021-08-07 04:04:14
ClearML Monitor: GPU monitoring failed getting GPU reading, switching off GPU monitoring
2021-08...

AgitatedDove14 it was executed with Python 3 and I’m running in venv mode.

Is it possible to set that at task enqueueing SuccessfulKoala55 ?

I’m not sure but it seems like you get different kinds of flexibility depending on whether you enqueue the task yourself or whether you rely on execute_remotely . I think ideally if I could choose to get the benefit of auto-scanning provided by execute_remotely as well as more flexibility it would be great.

For your second question, those are generated using custom tooling, it relies on the build system to be setup which is guaranteed by the docker image used. So I don’t think this is a case of supporting a specific env setup or build tool but just allowing custom script for env setup step / building code.
WDYT?

That won’t work 😕
The docker shell script runs too early in the process.
I want to inject a bash command after the repo has been clone (and maybe even after the venv has been installed).

TimelyPenguin76 After creating the venv (so I don’t have to do it myself). Once an env is there, I need to run a script while the env is activated from the root of the repo.

So when the repo is cloned and venv is created and activated I want to executed this from the repo: tools/setup_dependencies.sh

I’m wondering, would an older version of the agent work well with a newer server version and vice-versa?

I tried with and without. I’m having the issue where if I run the task from the queue it will complete as soon as it goes into docker but if I run the same docker run it works.