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
Hello Clearml Friends. I'M Trying To Setup A Clearml Agent On My Workstation To Queue Jobs On My Gpu.

Hello ClearML friends. I'm trying to setup a clearml agent on my workstation to queue jobs on my GPU.
$ pip3 install clearml-agent $ clearml-agent init $ clearml-agent daemon --detached --gpus 0 --queue <my queue name> --docker nvidia/cuda:10.1-cudnn7-runtime-ubuntu18.04However, when trying to queue a job I'm getting
docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create: dial unix /var/run/docker.sock: connect: permission denied. See 'docker run --help'. 2021-06-14 16:20:10 Process failed, exit code 126How can I give the clearml agent permission to run Docker commands? I enabled non-root access to Docker for my user (which I used to deploy the clearml agent). Did I miss something?

Setup on the workstation:
Ubuntu 20.04 GPU 0 - Titan RTX GPU 1 - GeForce RTX 2080 ti Python 3.8.5 CUDA Version: 11.2
(Note, one thing I notice is that my CUDA versions don't match. However, I would have expected that to give me a CUDA related error, not a Docker sock permissions error)

Posted 2 years ago
Votes Newest

Answers 5

I dip in and out of Docker, and that one gets me almost every time!

Posted 2 years ago

Thanks VivaciousPenguin66 and AgitatedDove14 . All is good now.

Posted 2 years ago

I think perhaps as standard, the group docker is already created.

The bit that isn't done is making your user part of that group.

Posted 2 years ago

You need to make sure the user is part of the docker group.
Follow these commands post install of Docker engine, and don't forget to restart the terminal session for the changes to take full effect .

` sudo groupadd docker

sudo usermod -aG docker ${USER} `Don't install Docker engine with root, your sysadmin will have kittens!

Posted 2 years ago

Hi IrritableOwl63
Yes this seems like a docker setup issue 🙂
either run the agent with sudo (not really recommended 😉 ) or add to suduers :

Posted 2 years ago