It's not that - there's probably something wrong in the pod configuration where the services agent is running since it fails launching a docker due to a socket issue

The 3 - is actually :- followed by --

What image should it be?

Doesn't matter - if not specified, the agent will use a default image (should be OK)

it has 3 “-” in the DAEMON_OPTIONS
PLus I don’t understand where is the repo for that image because the repo allegroai/clearml-agent has a different entrypoint file

It seems like the agent tries to spin up a docker image but fails since docker is not configured in the pod

Yeah, it seems this is an issue with the services agent in the helm chart - can you please open an issue in the helm repo and we'll try to handle it there?

but it also has the --create-queue flag but it didn’t create the queue I needed to create it manually

all the api use gunicorn

You think it’s the “--services-mode” flag?

Maybe this?
It’s the entrypoint file for the docker

That's strange as well - we'll need to try and reproduce it

When running with --local True
everything works btw… but locally 🙃

and when I try to do this

why locally it doesn’t try to run docker?

How are you running your server?

The agent has a preconfigured default docker image name

I believe because of this

Can you point me to the direction maybe?
I already made changes in the clearml-server repo and made my own image for the helm-charts… maybe I could fix this as well

One moment

SuccessfulKoala55
This is the error

Ooo oops

Sure no problem thanks!

helm charts

Works when the task is running locally

What do you mean?

This happens

I only enabled the pod and created services queue

But why does it try to run “docker run”?