Cloudflare Developers•5mo ago

Error checking 8080: The container is not listening in the TCP address 10.0.0.1:8080

I encountered an error where the container wasn't listening on the default port I had set in both the index.ts file and the Dockerfile. I've double-checked my configuration and code multiple times, but I still can't spot the issue. If anyone has faced a similar problem before, I’d really appreciate it if you could share your insights. Thank you! Observability

Error checking 8080: The container is not listening in the TCP address 10.0.0.1:8080

Error checking 8080: The container is not listening in the TCP address 10.0.0.1:8080

wrangler.jsonb

{    
    "containers": [{
        "name": "transformer",
        "image": "./Dockerfile",
        "class_name": "Transformer",
        "max_instances": 2,
        "instance_type": "dev"
    }]
}

{    
    "containers": [{
        "name": "transformer",
        "image": "./Dockerfile",
        "class_name": "Transformer",
        "max_instances": 2,
        "instance_type": "dev"
    }]
}

11 Replies

slice•5mo ago

I might be not correct but, your transformer class mentions port 2319 and your Dockerfile exposes 8080 did you have a look at that ?

AngkorOP•5mo ago

hi @slice I modified the file for testing and I forgot to update it. I have set the port to 8080 for Dockerfile and the container.

AngkorOP•5mo ago

This is the updated index.ts , I created the notification in R2 and trigger the queue to call to the container. I'm not sure if it is the best practice to use the container this way.

slice•5mo ago

does it work ?

AngkorOP•5mo ago

NO 😦

AngkorOP•5mo ago

And this is from container log

slice•5mo ago

this shows it's working 🤔

robert@moyai.ai•5mo ago

I have a similar issue Im opening my port on 8000. Also dont understand why you cant set the IP of the healthcheck. I have a loadbalancer (uvicorn) running in the container that I cant switch to 10.0.0.1

iamnogamer•3mo ago

Hello, reviving an old thread. Did you figure this out in the end? I believe I'm having a similar problem, seeing "Listening on vm(4294967295):2319" on container logs, and "Error checking 2368: The container is not listening in the TCP address 10.0.0.1:2368" on worker logs. Also "Error: Container crashed while checking for ports, did you setup the entrypoint correctly?". I've tried changing my port from 2368 to 2319 and that didn't help, only the error message changed to "Error checking 2319: The container is not listening in the TCP address 10.0.0.1:2319"

delivery•3mo ago

I'm getting this too, any luck?

Gaming

Programming

Error checking 8080: The container is not listening in the TCP address 10.0.0.1:8080

Did you find this page helpful?