Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hi, How Can I Pass A Env Variable To The Docker That'S Running The Agent When I Run This? I'M Havving Issues With The Agent'S Git Clone Where It Requires Sslverification To Be Disabled. Clearml-Agent Daemon --Gpus 0 --Queue Gpu --Docker --Foreground

Hi, how can i pass a env variable to the docker that's running the agent when i run this? I'm havving issues with the agent's git clone where it requires sslverification to be disabled.
clearml-agent daemon --gpus 0 --queue gpu --docker --foreground

  
  
Posted 3 years ago
Votes Newest

Answers 4


Sorry take back. Just realised that this argument only worked on running the agent, but when you enqueue a task into this agent, the argument is not passed on to the container that the agent spawned.

This is the same issue for the docker image. It reverts back to nvidia/cuda:10.1-runtime-ubuntu18.04 despite me setting something else.

  
  
Posted 3 years ago

Executing task id [228caa5d25d94ac5aa10fa7e1d02f03c]:
repository = https://192.168.50.88:18443/tkahsion/pytorchmnist
branch = master
version_num = cfb833bcc70f3e10d3b6a96cfad3225ed682382b
tag = 
docker_cmd = nvidia/cuda:10.1-runtime-ubuntu18.04
entry_point = pytorch_mnist.py
working_dir = .
Warning: could not locate requested Python version 3.9, reverting to version 3.6
Using base prefix '/usr'
New python executable in /root/.clearml/venvs-builds/3.6/bin/python3.6
Also creating executable in /root/.clearml/venvs-builds/3.6/bin/python
Installing setuptools, pip, wheel...
done.
cloning: https://192.168.50.88:18443/tkahsion/pytorchmnist
fatal: unable to access ' https://192.168.50.88:18443/tkahsion/pytorchmnist/ ': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Repository cloning failed: Command '['clone', ' https://192.168.50.88:18443/tkahsion/pytorchmnist ', '/root/.clearml/vcs-cache/pytorchmnist.f220373e7227ec760b28c7f4cd99b534/pytorchmnist', '--quiet', '--recursive']' returned non-zero exit status 128.
clearml_agent: ERROR: Failed cloning repository. 

  1. Make sure you pushed the requested commit:
    (repository=' https://192.168.50.88:18443/tkahsion/pytorchmnist ', branch='master', commit_id='cfb833bcc70f3e10d3b6a96cfad3225ed682382b', tag='', docker_cmd='nvidia/cuda:10.1-runtime-ubuntu18.04', entry_point='pytorch_mnist.py', working_dir='.')
  2. Check if remote-worker has valid credentials [see worker configuration file]
    User aborted: stopping task (3)
    Leaving process id 23081
    DONE: Running task '228caa5d25d94ac5aa10fa7e1d02f03c' (user aborted)
  
  
Posted 3 years ago

Any advice on this?

  
  
Posted 3 years ago

After some churning, this is the answer. Change it in the clearml-agent init generated clearml.conf.

` default_docker: {
    # default docker image to use when running in docker mode
    image: "nvidia/cuda:10.1-runtime-ubuntu18.04"

    # optional arguments to pass to docker image
    # arguments: ["--ipc=host", ]
    arguments: ["--env GIT_SSL_NO_VERIFY=true",]
  } `

  
  
Posted 3 years ago
1K Views
4 Answers
3 years ago
one year ago
Tags