sure AgitatedDove14
cleaml-session:
` $ clearml-session --queue session-test  ✔
clearml-session - CLI for launching JupyterLab / VSCode on a remote machine
Verifying credentials
Use previous queue (resource) 'session-test' [Y]/n? y

Interactive session config:
{
"base_task_id": null,
"git_credentials": false,
"jupyter_lab": true,
"keepalive": false,
"password": "263d75e1e32c855893740d23ec000c5abfb9d3c4d50506ab87229d0...

Thanks Martin; I’m really enyjoying clearML so far. Especially the function to execute code remotely makes it a real great product 🎉

Thank you very much for your quick reply! Im using mac on my local machine and the agent is running on a linux vm (debian)

Thanks for this information! Then I know that it must have something to do with the conda installation. I will dig deeper on that and will post an update, if I’m successful - maybe it would be helpful for someone else in the future

these are the last few lines from the console output - if it is helpful:
` Current configuration (clearml_agent v1.5.0, location: /tmp/clearml.conf):

api.version = 1.5
api.verify_certificate = true
api.default_version = 1.5
api.http.max_req_size = 15728640
api.http.retries.total = 240
api.http.retries.connect = 240
api.http.retries.read = 240
api.http.retries.redirect = 240
api.http.retries.status = 240
api.http.retries.backoff_factor = 1.0
api.http.retries.backoff_max ...

Yes, will do! Does it matter for the agent if it runs in docker mode? I think not, right?

and both works when I ignore the SSH tunneling failed, retrying in 3 seconds - warning and tunnel manually

Hi Martin! I’m running the agent in docker-mode 🙂

Thanks for your time, Martin! It is now working under the premise that I
start the clearml-agent in docker-mode as root user change the sshd_config so that it allows port forwarding , agent forwarding and x11 forwarding start clearml-session on my local machine as root

I deployed a new instance real quick and installed everything again. Conda gets found via which conda and is also listed when I try it with echo $PATH . The error still persists.