Cloudflare Developers•6mo ago

Getting: Failed to start container: The container is not running, consider calling start()

Fflof.fly Getting: Failed to start container: The container is not running, consider calli...

flof.flyOP•7/12/25, 12:24 PM

Issue was related to my Dockerfile, fixed the COPY part

RRafal 👋 I'm trying to run Sandbox. I'm failing to use Dockerfile from node_modules s...

ldl•7/13/25, 1:15 AM

I have the same problem

IIdyll So... I've managed to get some interesting proof-of-concept stuff going with con...

Beny•7/13/25, 8:21 AM

We are using the websocket method. It works pretty well.
You can also run a local worker inside the container with remote bindings to access things like R2 and D1. Hyperdrive isn't supported with remote bindings yet but is being worked on

flof.flyOP•7/13/25, 8:38 AM

Hey, I'm working Locally with Worker invoking a Workflow invoking a Container.

It seems to me that Workflows are Docker Containers when executed locally, and Container is also up&running in localhost:8080 (i can reach it using postman i.e)

But seems that the Workflow's container is unable to see the Container's container.

I get the following error in localhost:

✘ [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

I tried changing hostname to 0.0.0.0:8080 but didn't change much.

Any help? Would love to share my wrangler config file.

This only applies in localhost, deployed works as expected.

Bbrainstorm I'm currently facing a cloudflare ports binding issue... despite specifying `808...

bomboclat•7/14/25, 8:23 AM

~~are you setting the defaultPort in the Container class? link~~

edit looked at the PR and yes you are

Cloudflare Docs

Env Vars and Secrets

Pass in environment variables and secrets to your container

Aniog•7/14/25, 9:00 AM

I wonder if there is any way to support starting dev server and hot updates with the code uploaded to containers using wrangler deploy now？

Bbrainstorm I looked at options through the wrangler.jsonc config, but there's none where yo...

bomboclat•7/14/25, 9:16 AM

Have you tried removing the extra port? just debugging by reducing the complexity of exposing two ports

Eelco•7/14/25, 9:42 AM

Facing the same connection issues locally on macos.

The container is mapped to 550XX -> 8080 and the worker says it can't connect to 8080. The ephemeral port mapping doesnt seem to work correctly. Since the worker can spin up multiple containers it shouldn't try to connect to 8080 directly but the mapped 550XX port.

Eelco•7/14/25, 10:01 AM

Downgrading to "@cloudflare/containers": "0.0.19", from 0.0.22 fixed it.

Eelco•7/14/25, 10:07 AM

I recon this is the issue.

https://github.com/cloudflare/containers/commit/0611bc7dcb0653b0c90c3fa9d0d6a00d31d0ae5d#diff-29f6935de7d89eec5929ebe8d3fb298265b320961523b05695398f0bc4ae729bR746

The request comes from localhost:8787. with this change instead of using the default port it will use the port of the original request 8787 and the container request fails

azeii•7/14/25, 12:34 PM

Does data transfer from Cloudflare Containers directly to Cloudflare R2 incur egress fees, or are requests "within Cloudflare" exempted from egress fees? https://developers.cloudflare.com/containers/pricing/#network-egress

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:

iddogino•7/14/25, 11:50 PM

@Mike Nomitch | Workers PM any news on the geographic placement issue you mentioned a couple of weeks back? I'm based in SF and getting almost exlusively Asia containers

Mike Nomitch•7/15/25, 12:24 AM

I tend to just do something similar to the main template (linked to from the UI), and then modify from there

Mike Nomitch•7/15/25, 12:24 AM

What’s the specific error?

Mike Nomitch•7/15/25, 12:25 AM

And sorry just went mobile so won’t be able to go in depth yet.

I’d share:

what environment is the issue happening in?
could it be some error bringing down the instance? (We’re working on exposing OOM messages better now)
setting right port in code and using Container class? Not Durable Object directly?

papiomenos•7/15/25, 9:29 AM

When will containers come to the free tier?

rye•7/15/25, 1:30 PM

Is there an ideal workflow to get containers working on "Workers for platforms"?

Bbrainstorm YES! Thank you, that seems to improve the situation @teekm ! I just exposed port...

flof.flyOP•7/15/25, 4:11 PM

What's the difference between containerFetch and fetch?

dustiiin•7/15/25, 10:18 PM

Hey, anyone knows if it is possible to regenerate files from deployed files?
I accidentally deleted my project files and now i dont know how to get them back.

aanchalogy•7/16/25, 8:03 AM

Hey, how to bind 2 workers which are running in same account ? I have a process running in 1 container and another worker need to call the api of container. however as the container and worker are in sam eaccount, it is not getting called. please help with solution

Elliot Hesp•7/16/25, 8:39 AM

Having some issues with my container locally resolving network requests - every so often they just hang. Works fine in prod.

EElliot Hesp Having some issues with my container locally resolving network requests - every ...

flof.flyOP•7/16/25, 9:44 AM

same

Elliot Hesp•7/16/25, 10:46 AM

My container has a /etc/resolv of my local ip, no clue whether this causes it (but also, its unexpected)

Kludex•7/16/25, 11:37 AM

It seems I'm not able to use the

start

start

and wait for the port to be up:

  await container.start({
    envVars: {} // The env vars
  })
  await container.startAndWaitForPorts(4000);

  await container.start({
    envVars: {} // The env vars
  })
  await container.startAndWaitForPorts(4000);

Can I define this

start

start

on the constructor? Is there an example?

willy•7/16/25, 4:36 PM

Hi there, new here - has anyone successfully wired a container to hyperdrive? I'm having name resolution trouble for the connectionString in the container

dave•7/16/25, 5:35 PM

So R2 bandwidth to/from containers is still billed right?

Ddave So R2 bandwidth to/from containers is still billed right?

Hard@Work•7/16/25, 5:41 PM

Correct

Elliot Hesp•7/16/25, 6:47 PM

Ok I'm 90% sure that reading a ReadableStream from container inside of the DO just doesn't work consistently

Elliot Hesp•7/16/25, 7:17 PM

Going to setup a reproduction, but I'm sure something is messed up

rye•7/16/25, 7:18 PM

Is there an ideal workflow to get containers working on "Workers for platforms"?

skifimba•7/16/25, 10:01 PM

Guys is this only me? Container is unable to start

Sskifimba Guys is this only me? Container is unable to start

John Spurlock•7/16/25, 10:04 PM

might be https://www.cloudflarestatus.com/incidents/dg4khdw4n3nx

Container applications are unable to start

skifimba•7/16/25, 10:05 PM

Ah i see thanks @John Spurlock didn't notice that on status page

Elliot Hesp•7/17/25, 9:22 AM

Just filed an issue - readable streams out of a container are super inconsistent for me https://github.com/cloudflare/containers/issues/53

GitHub

Unable to proxy ReadableStream to client · Issue #53 · cloudflare...

Hey all, I'm experiencing an issue streaming results from a container to a client. I have a reproduction of the following issue with instructions: https://github.com/Ehesp/cf-containers-repro M...

karimulm•7/17/25, 7:29 PM

Is hyperdrive accessible from cloudflare container?

Kkarimulm Is hyperdrive accessible from cloudflare container?

John Spurlock•7/17/25, 7:39 PM

can we connect to the hyperdrive using

Carl Peaslee•7/17/25, 9:32 PM

Hey does anyone have an example that works locally? I cannot get to "container images ready"

つ

つんでれd•7/17/25, 10:25 PM

I ran into the same issue on localhost and was able to resolve it by explicitly setting the port using switchPortswitchPort, rather than downgrading or using containerFetch()containerFetch(). However, it does seem like a design inconsistency that the port must always be specified in local environments but not in production.

I see that these changes were introduced because Durable Objects currently don’t support WebSockets from non-default JSRPC methods. I was thinking it might be cleaner to handle this by overriding the

fetch()

fetch()

method using a helper from @cloudflare/containers@cloudflare/containers, like this:

import { extractPort } from '@cloudflare/containers';

override async fetch(request: Request): Promise<Response> {
  return this.containerFetch(request, extractPort(request));
}

import { extractPort } from '@cloudflare/containers';

override async fetch(request: Request): Promise<Response> {
  return this.containerFetch(request, extractPort(request));
}

Getting: Failed to start container: The container is not running, consider calling start()

Similar Threads

Similar Threads

Similar Threads