This is clearml-agent helm chart values.yaml file i used to install

Are there other people experiencing the same issue as me?

I set CLEARML_AGENT_UPDATE_VERSION=1.5.3rc2 ` in agentk8sglue.basePodTemplate.env as i mentioned

i understand the reason that clearml-session supports only cli is because of SSH. right? i thought it was easy to develop sdk. instead, i can use your recommendation

I want to get task id, properties right after submitting clearml-session task

I’m also curious if it’s available to bind the same GPU to multiple queues.

Wow i appreciate that 😆

Hope clearml-session will be more developed as clearml-agent. cause it is so useful! 👍
My issue: None

@<1523701070390366208:profile|CostlyOstrich36> Hello. Oh, sorry for the lack of explanation.when i execute the command “clearml-session ~“, jupyter url format is ‘ None :{local_jupyter_port}/?token={jupyter_token}’ and vs code url format is just ‘ None :{local_vscode_port}’ like the pic i attached here. I wonder why vs code url doesn’t have token.

@<1523701205467926528:profile|AgitatedDove14> Good! I will try it

Thanks! also logs too?

can i hide some of them without fixing and rebuilding docker image?

Hi @<1523701205467926528:profile|AgitatedDove14>
The server is already self hosted. I realized i can’t create a report using clearml sdk. so i think i need to find other ways

then, is there any way to get embed code from scalars?

@<1523701205467926528:profile|AgitatedDove14> @<1529271085315395584:profile|AmusedCat74> Hi guys 🙌

• I think that by default it uses the host network so it can take care of that, are you saying you added k8s integration ?-> Yes, i modified clearml-agent helm chart.
• “SSH allows access with password” it is a very long random password, not sure I see a risk here, wdyt?-> Currently, when enqueueing a task, clearml-session generates a long random password for SSH and VS Code and...

i am having same issue: None

The clearml server I installed is a self-hosted server, and developers log in using a fixed ID and password for authentication. That’s it!

Futhermore, to access ssh/vscode/jupyterlab directly without ssh tunneling, I modified the clearml-session script, and once I upload this script to the DevOps project in draft status, developers clone it to their own project. Then, they enqueue and wait for the command and URL to access ssh/vscode/jupyterlab, which will be displayed.

It seems that there is no way to add environments, so i customized charts and using it on my own.

it’s been working well until i removed virtualenv and recreated, then i reinstall only clearml and clearml-session

clearml==1.9.2
clearml-session==0.4.0

wow ! thank you for quick answer! it worked like a charm. have a nice day:)

i fount the solution!! i added configuration to helm’s values.yaml below.

additionalConfigs:
# services.conf: |
# tasks {
# non_responsive_tasks_watchdog {
# # In-progress tasks that haven’t been updated for at least ‘value’ seconds will be stopped by the watchdog
# threshold_sec: 21000
# # Watchdog will sleep for this number of seconds after each cycle
# watch_interval_sec: 900
# }
# }
apiserver.co...

hello CostlyOstrich36 unfortunately, i also did it to api server just in case. but didn’t work

Oh, it didn’t generate conf file properly. I will try again

thank you CostlyOstrich36

I tried using K8S_GLUE_POD_AGENT_INSTALL_ARGS=1.5.3rc2 instead of CLEARML_AGENT_UPDATE_VERSION=1.5.3rc2 , but it’s same. doesn’t read gpu usage.. 🥲

I tried the suggestion you mentioned, but it’s the same. And it doesn’t seem to be an AMI issue. The same problem is occurring even in an on-premise environment.

@<1523701087100473344:profile|SuccessfulKoala55> I realized that this is not an issue with the cloud or on-premise environment. it’s working well on gke but not working on eks. here is the log when i run “clearml-agent daemon --queue ~” command on eks

root@shelley-gpu-pod:/# clearml-agent daemon --queue shelley3
/usr/local/lib/python3.8/dist-packages/requests/init.py:109: RequestsDependencyWarning: urllib3 (2.0.1) or chardet (None)/charset_normalizer (3.1.0) doesn’t match a supported ve...