And I checked, both envs are set in the agents pod

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

SuccessfulKoala55 Seems like apiserver uses redis as cache for ui pagination with a long ttl

Sure no problem thanks!

why locally it doesn’t try to run docker?

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

One of the keys:
b”<class ‘apiserver.database.model.base.GetMixin.GetManyScrollState’>/f4010ba7df0f45dbbea10a71fe568a94"

Thanks… didn’t look at the image 😅

Thanks for the reply 👍

One moment

I’ll test without parentheses

With

What do you mean?

Hi SuccessfulKoala55 ,

On the agent pod the tasks logs are written locally to /tmp/.clearml_agent_out.<random num>.txt

I wan’t those logs to also bind to the hosts stdout, with a console handler for example

sure

I believe because of this

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

cloned the repo “clearml-helm-charts”

maybe change the session cookie to 24 hours?

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

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

Works when the task is running locally

The cookie has a ttl of 3000+ years…

all the api use gunicorn

I see some keys from apiserver that are a couple of hundreds of mb

I only enabled the pod and created services queue

helm charts