when you spin a container , you map a host port with a container port using -p parameter
docker run -v ~/clearml.conf:/root/clearml.conf -p 8080:8080 -e CLEARML_SERVING_TASK_ID =<service_id> -e CLEARML_SERVING_POLL_FREQ =5 clearml-serving-inference:latest
Here you map your computer's port 8080 with the container port 8080. If your 8080 port is already used, you can use another, using for example -p 8081:8080

Here's what I get for the initial set up stage of clearml-serving

SweetBadger76 I'm following the docs, is this the expected output?

DefiantHippopotamus88 did you get it working?

AgitatedDove14 Doesn't look like the same error as that thread.

Let's maybe join our effort to get local deployment?

hi WickedElephant66
I have the same issue, but port is not the only problem
https://clearml.slack.com/archives/CTK20V944/p1656446563854059

Hey,
So I did change the host port on the docker -compose.yml file, here's the weird error:
Why is the url being parsed with “”
I have renamed example. en v to just .env so that docker -compose can recognise the env variables(—env-file never works for me)

I'm running the clearml server on my machine, self hosted

I'm not, not sure about WickedElephant66 / DefiantHippopotamus88

hey Martin,
DefiantHippopotamus88 joined the thread. He faced the same issue in the thread you sent
https://clearml.slack.com/archives/CTK20V944/p1656537337804619?thread_ts=1656446563.854059&cid=CTK20V944

TenderCoyote78 i pm you to avoid overfilling the thread here

Removing the “” in my env file gives me a timeout issue

So I'd have to make edits to the docker-compose file for clearml-serving; there would not be any issues arising due to that right?

AgitatedDove14 are you using wsl setup?

Wdym?

Im using the clearml-serving for repo and running the docker-compose file there to set it tip ,
But im also running the clearml server on my machine self - hosted

Oh okay

can you share your logs ?

I'm facing the issue during the initial set up of clearml serving - i.e the step where you use docker-compose to launch the serving containers

Or is something wrong here

it worked for me with one docker-compose for all

WickedElephant66 is this issue the same as this one?
https://clearml.slack.com/archives/CTK20V944/p1656537337804619?thread_ts=1656446563.854059&cid=CTK20V944

at least no more auth errors

can you do docker ps to check if there are running containers that already bind the port ?