I am getting this error `The container is not listening in the TCP address 10.0.0.1:3000` but when t

I am getting this error

The container is not listening in the TCP address 10.0.0.1:3000

The container is not listening in the TCP address 10.0.0.1:3000

The container is not listening in the TCP address 10.0.0.1:3000

The container is not listening in the TCP address 10.0.0.1:3000 but when the docker image is running it is listening on port 3000 hence the server log

[2025-06-26 18:14:25] INFO WEBrick::HTTPServer#start: pid=188 port=3000

[2025-06-26 18:14:25] INFO WEBrick::HTTPServer#start: pid=188 port=3000

[2025-06-26 18:14:25] INFO WEBrick::HTTPServer#start: pid=188 port=3000

[2025-06-26 18:14:25] INFO WEBrick::HTTPServer#start: pid=188 port=3000

This is my code

import { Container, getContainer } from "@cloudflare/containers"

export class MyContainer extends Container {
    defaultPort = 3000
    sleepAfter = "1h"
    envVars = {
        DB_HOST: this.env.DB_HOST,
        DB_USERNAME: this.env.DB_USERNAME,
        DB_PASSWORD: this.env.DB_PASSWORD,
        DB_DATABASE: this.env.DB_DATABASE,
    }
}

export default {
    async fetch(request: Request, env: Env): Promise<Response> {
        const container = getContainer(env.MY_CONTAINER)
        return container.fetch(request)
    },
}

import { Container, getContainer } from "@cloudflare/containers"

export class MyContainer extends Container {
    defaultPort = 3000
    sleepAfter = "1h"
    envVars = {
        DB_HOST: this.env.DB_HOST,
        DB_USERNAME: this.env.DB_USERNAME,
        DB_PASSWORD: this.env.DB_PASSWORD,
        DB_DATABASE: this.env.DB_DATABASE,
    }
}

export default {
    async fetch(request: Request, env: Env): Promise<Response> {
        const container = getContainer(env.MY_CONTAINER)
        return container.fetch(request)
    },
}

import { Container, getContainer } from "@cloudflare/containers"

export class MyContainer extends Container {
    defaultPort = 3000
    sleepAfter = "1h"
    envVars = {
        DB_HOST: this.env.DB_HOST,
        DB_USERNAME: this.env.DB_USERNAME,
        DB_PASSWORD: this.env.DB_PASSWORD,
        DB_DATABASE: this.env.DB_DATABASE,
    }
}

export default {
    async fetch(request: Request, env: Env): Promise<Response> {
        const container = getContainer(env.MY_CONTAINER)
        return container.fetch(request)
    },
}

import { Container, getContainer } from "@cloudflare/containers"

export class MyContainer extends Container {
    defaultPort = 3000
    sleepAfter = "1h"
    envVars = {
        DB_HOST: this.env.DB_HOST,
        DB_USERNAME: this.env.DB_USERNAME,
        DB_PASSWORD: this.env.DB_PASSWORD,
        DB_DATABASE: this.env.DB_DATABASE,
    }
}

export default {
    async fetch(request: Request, env: Env): Promise<Response> {
        const container = getContainer(env.MY_CONTAINER)
        return container.fetch(request)
    },
}

What should I try?

Ssurgery18 I am getting this error `The container is not listening in the TCP address 10.0....

ItsWendell•6/26/25, 10:54 PM

What Dockerimage are you trying to run? Ensure it has EXPOSE 3000EXPOSE 3000 in the Dockerfile and that your wrangler.json is properly set up and that the logs from

wrangler dev

wrangler dev

are showing a proper build of your image.

IItsWendell What Dockerimage are you trying to run? Ensure it has `EXPOSE 3000` in the Docke...

surgery18OP•6/26/25, 11:03 PM

The end of the Dockerfile is

EXPOSE 3000
CMD ["rails", "server", "-b", "0.0.0.0"]

EXPOSE 3000
CMD ["rails", "server", "-b", "0.0.0.0"]

surgery18OP•6/26/25, 11:04 PM

And the build was successful and pushed to cloudflare and it does run saying the server is running at 3000 port.

surgery18OP•6/26/25, 11:04 PM

So that is the strange thing

iddogino•6/26/25, 11:12 PM

I am actually running into an issue that might be similar / related to @surgery18 's issue
I have a Dockerfile which similarly ends with:

EXPOSE 8080
ENTRYPOINT ["node", "index.mjs"]

EXPOSE 8080
ENTRYPOINT ["node", "index.mjs"]

When I run it locally everytime I get a container I see in the logs:

✘ [ERROR] Error checking if container is ready: connect(): Connection refused: container port not found. Make sure you exposed the port in your container definition.
✘ [ERROR] Error checking if container is ready: The operation was aborted

✘ [ERROR] Error checking if container is ready: connect(): Connection refused: container port not found. Make sure you exposed the port in your container definition.
✘ [ERROR] Error checking if container is ready: The operation was aborted

Oddly enough right after that I actually get the Port 8080 is readyPort 8080 is ready message and the request does work. But when I try to deploy and run -- nada... I just see this:

Error checking if container is ready: There is no container instance that can be provided to this durable object, try again later or scale the application

Error checking if container is ready: There is no container instance that can be provided to this durable object, try again later or scale the application

DDefenestrator Do you have the port set on your Container class?

iddogino•6/26/25, 11:17 PM

I havr the default port but not the requiredPorts - what are those?

DDefenestrator Has anyone managed to get even a basic android app build running on a container?...

ItsWendell•6/26/25, 11:55 PM

I think builds could be a relatively good use case, but maybe relatively expensive compared to other solutions / providers. The storage space in the beta is quite low (4GB) and from experience I know that the dependencies needed for android builds can be huge, also ensure you've set the instance type to standard.

Maybe there are existing solutions to use S3 / R2 for storage during builds that could prevent the disk from becoming full.

ItsWendell•6/27/25, 12:06 AM

It's early and bigger instances are coming! It would be good to get a grasp of the exact disk space you need and where in your file system you see it grow the most during the build to see what's possible over time. I think for now with the amount of vCPUs available and the space you're going to have to wait a long time for your android built to complete, setting something up with Github Actions or Google Cloud Run would be better.

DDefenestrator I don't think the requiredPorts are needed, was one of the many things I tried. ...

iddogino•6/27/25, 12:32 AM

I tried adding back the requiredPorts and as you suspected it didn't make a difference... Any other ideas you tried?

DDefenestrator It’s definitely standard; I spent a fair bit of time slimming down the docker im...

1984 Ford Laser•6/27/25, 1:29 AM

One of the devs mentioned somewhere that the ability to mount an R2 bucket in the container directly is something they're looking at. Personally that would be a huge efficiency improvement, especially if the R2 bucket is co-located with the Worker/DO/Container for maximum speed

Sameer Ali•6/27/25, 1:49 AM

i just deployed a very first worker with container, but its been about 30 minutes, the instance status is stuck at inactive. is that normal?

Sameer Ali•6/27/25, 1:49 AM

container status is Ready

Sameer Ali•6/27/25, 2:56 AM

finally got it up and running, after more than an hour.

SKUZZIE•6/27/25, 4:46 AM

Is there an example for manually making a request to a container from a worker instead of just proxying a request? This is a really cool product btw

Edit: Nevermind, this worked. Although it'd be nice to have a nicer API for doing this:

await container.fetch(
    "http://localhost:3000/transcode",
    {
        method: "POST",
        body: object.body,
    },
);

await container.fetch(
    "http://localhost:3000/transcode",
    {
        method: "POST",
        body: object.body,
    },
);

Iiddogino I am actually running into an issue that might be similar / related to @surgery1...

windsor nguyen•6/27/25, 6:00 AM

also getting this issue. works locally but not when deployed. has anyone found a fix?

Iiddogino I am actually running into an issue that might be similar / related to @surgery1...

stt9015•6/27/25, 6:01 AM

I am getting this exact same problem "Error checking if container is ready: There is no container instance that can be provided to this durable object, try again later or scale the application". Each time I make a request to my worker, a new instance ID is correctly created in the instance list. However, its state is immediately set to Inactive. It never enters a Running state, and the "Live Instances" count remains at 0.

SSameer Ali finally got it up and running, after more than an hour.

stt9015•6/27/25, 10:16 AM

What did you do to get it working? Feel like I’m in a similar boat

ldl•6/27/25, 10:35 AM

I'm having an issue with container configuration where instance_typeinstance_type setting isn't working:

"containers": [
  {
    "class_name": "MyContainer",
    "image": "./Dockerfile", 
    "max_instances": 5,
    "instance_type": "basic",
    "name": "n8n-container"
  }
]

"containers": [
  {
    "class_name": "MyContainer",
    "image": "./Dockerfile", 
    "max_instances": 5,
    "instance_type": "basic",
    "name": "n8n-container"
  }
]

the "instance_type": "basic""instance_type": "basic" configuration doesn't seem to take effect - the container still uses default settings.

Does anyone know the correct way to configure this? Or is this field name even correct?

Dawson•6/27/25, 11:10 AM

is the pricing public yet?

Dawson•6/27/25, 11:11 AM

https://developers.cloudflare.com/containers/pricing/

Cloudflare Docs

Pricing

Containers are billed for every 10ms that they are actively running at the following rates, with included monthly usage as part of the $5 USD per month Workers Paid plan:

Dawson•6/27/25, 11:11 AM

ah yes it is

Dawson•6/27/25, 11:26 AM

Does anyone have some real cost estimates? I host about 12 projects on a VPS atm, and have no idea if it would be cheaper to run on cf containers. These are all dynamic nextjs apps with a trpc + bun backend. I have no idea where to start with calculating how many CPU / ram minutes my app uses

DDawson Does anyone have some real cost estimates? I host about 12 projects on a VPS atm...

John Spurlock•6/27/25, 11:30 AM

cost of the dev instance running for 30 days: $5.25, basic: $20.16, standard: $52.56 - imo this service isn't really meant to replace a long-running vps, it's more for bursty use-cases and things that would benefit from running on cf's network

Dawson•6/27/25, 11:31 AM

Hmmm okay. Thank you

I do have a few things that would benefit from this though so I will 100% be checking this out

Dawson•6/27/25, 11:31 AM

Very cool platform you all have here

nickmundel•6/27/25, 11:36 AM

Hey all, I have a quick. or longer question depending on the answer, but I have a problem with internet connectivity. I have the following setup: a go web server as a sort of API with API-keys, etc and a route which makes use of typst to generate me PDF from text. Typst has quite the large package ecosystem and to fetch those from their package registry it needs internet connectivity. I followed the docs trying to set enableInternet: true in the Durable Object when starting the container. The problem is it just doesnt work, I create a quick script in the docker container to ping a few websites, but they all fail because they dont find a route to these websites. Im at a loss at the moment, if needed I can post my current DO setup if that help. Thank you for your help!

JeanSebTr•6/27/25, 2:28 PM

The April blog post announcement had a code snippet using enableInternet: falseenableInternet: false with a callback named onContainerRequestonContainerRequest for fetch requests to the configured workersAddressworkersAddress from inside the container

Is it something that's actually supported? I wasn't able to find anything in the documentation, generated types or the @cloudflare/containers@cloudflare/containers repo

JJeanSebTr The April blog post announcement had a code snippet using `enableInternet: fals...

nickmundel•6/27/25, 2:34 PM

Yeah I dont think so at the moment, there is also a Thread in this channel about that which states that it is not supported. But I believe that that has nothing to do with general internet connectivity, rather than setting up something more complicated between workers

KKZ actually nm i think they are coming up wih something better listenTcp @6 (filter...

KZ•6/27/25, 2:41 PM

@JeanSebTr@nickmundel not implemented yet

nickmundel•6/27/25, 2:42 PM

@KZ but that hasn't anything to do with Internet connectivity, right?

Nnickmundel @KZ but that hasn't anything to do with Internet connectivity, right?

KZ•6/27/25, 2:46 PM

@JeanSebTr's is about controlling the container prevent outbound to public but enable within cloudflare. enableInternet:false should work but they don't have the listenTcp yet. i had the same question because of the blog article had to dive into workerd code to see it wasn't implemented. confirmed the PM building that functionality out

JJeanSebTr The April blog post announcement had a code snippet using `enableInternet: fals...

KZ•6/27/25, 2:51 PM

something else to see is that they're releasing https://blog.cloudflare.com/workers-virtual-private-cloud/ maybe soon. its possible that durableobjects will be part of that in which i would think this would fall under the containers

KKZ @JeanSebTr's is about controlling the container prevent outbound to public but e...

JeanSebTr•6/27/25, 3:19 PM

Thanks for the info! It would be great for the container to be able to call its DurableObject. Would simplify coordination if the container can push state when required instead of maintaining websockets or polling for progress

Sstt9015 What did you do to get it working? Feel like I’m in a similar boat

Sameer Ali•6/27/25, 5:09 PM

i guess, it took its time to provision the instance.

Ssurgery18 I am getting this error `The container is not listening in the TCP address 10.0....

surgery18OP•6/27/25, 6:08 PM

Has anyone solved this kind of error yet? Would love ideas on what to try to get it working.

DDefenestrator I don't think the requiredPorts are needed, was one of the many things I tried. ...

SKUZZIE•6/27/25, 8:13 PM

That fixed it for me, thanks! This should get added to the docs...
Edit: JK the error came back

Ssurgery18 Has anyone solved this kind of error yet? Would love ideas on what to try to get...

Francisco Hermida•6/27/25, 9:16 PM

I was having the same exact error as you "The container is not listening in the TCP address", sometimes it would connect sometimes not, "A call ... waited for too long". I went to sleep woke up tried again and it worked. Very weird

FFrancisco Hermida I was having the same exact error as you "The container is not listening in the ...

surgery18OP•6/27/25, 9:22 PM

Interesting. Mine hasn't even worked once yet. Just the errors being shown.

Ssurgery18 Interesting. Mine hasn't even worked once yet. Just the errors being shown.

Francisco Hermida•6/27/25, 9:28 PM

Most likely an issue on cloudflare's side

FFrancisco Hermida Most likely an issue on cloudflare's side

surgery18OP•6/27/25, 9:40 PM

So I JUST managed to fix it thanks to @Thomas Lefebvre and the issue was the instance type needed to be bigger. So instead of the default dev size, it needed to be the basic type. So @Francisco Hermida try using the basic instance_type. I think it is because the docker image might need to consume more memory then what is available on the dev type. That is my guess. So maybe you should try that too to see if it fixes your issue if it comes back for you.

Ssurgery18 So I JUST managed to fix it thanks to @Thomas Lefebvre and the issue was the ins...

Francisco Hermida•6/27/25, 9:47 PM

I already had my instance type set to the largest yesterday. Maybe the change took a really long time to take effect? I probably played with it for at least 30 minutes after changing to a larger instance. Thanks for sharing will keep it in mind if it comes back.

FFrancisco Hermida I already had my instance type set to the largest yesterday. Maybe the change to...

1984 Ford Laser•6/27/25, 11:28 PM

Did you spawn a new instance after making the change? I imagine an instance of a container can't have its instance type changed once its been created the first time

I am getting this error `The container is not listening in the TCP address 10.0.0.1:3000` but when t

Similar Threads

Similar Threads

Similar Threads