@<1523701205467926528:profile|AgitatedDove14> actually no. I was unaware that was needed. I will try that and let you know

@<1523701087100473344:profile|SuccessfulKoala55> the docker user is root, but it does not have the "sudo" group if that's what you mean. Is that required?

EDIT: I just ran "sudo ls" and it returned with no issues so I guess I do have sudo permission :man-shrugging:

Ideally, I would've wanted to use the GUI to sent shutdown/restart signals to the worker itself similar to what I currently do with tasks. From I understand, this is not possible so I would settle for maybe just adding an easier way to find what command to run to kill a certain worker. Even a simple button in the workers/queues GUI to copy a worker's ID and Name would make things easier.

I have a preprocessing task that is CPU parallelized, but I wanted to create a ClearML task for each instance since it reports some parameters that I want to later aggregate. Running this quickly requires 10-30 agents listening on the same queue

that's an interesting use case for services mode. I'll try it out. thanks!

yes.

I checked the base docker image I use and noticed that a $HOME/.gitconfig file already exists. would that be an issue given that the .gitconfig of the current user is mounted to that path once the clearml task is run?

these are the mounts I add:
-v /home/some_username/workspace/:/root/workspace -v /software:/software -v /images:/images -v /data:/data -v /processedData:/processedData -v /disk1:/disk1 -v /disk2:/disk2 -v /disk3:/disk3 -v /disk4:/disk4 -v /disk5:/disk5 -v /disk6:/disk6 -v /disk8:/disk8

None of these seem problematic to me. The only issue I can think of is that /home is an external mount on the host machine (outside of docker). Should I mount it somewhere?

it is /home This is how we share user dirs across multiple servers. I think this might be a permissions issue though. will try changing the permissions on .gitconfig and let you know if that helps

@<1533257407419912192:profile|DilapidatedDucks58> I'm had the same issue and solved it by removing the server's CORS config (from any config file under /opt/clearml/config).

see this thread for details: None )

@<1523701070390366208:profile|CostlyOstrich36> @<1523701087100473344:profile|SuccessfulKoala55> any idea how to fix this?