does it work for local dev?

G

goofysystem•9/25/25, 10:06 PM

its not working for local dev. I run

wrangler dev

wrangler dev

and it just gets stuck on build and hangs, but if I run a

docker build

docker build

docker build

docker build container gets built in a reasonable time.

G

gruntlord6OP•9/25/25, 10:11 PM

hmm thats all I've got, whenever that happens it was always docker desktop for me. Just to check, your on the latest version of wrangler?

G

goofysystem•9/25/25, 10:12 PM

@gruntlord6 yup. I just confirmed on a smaller project that my go continer builds correctly. Maybe I'm hitting some memory limit or constraints idk?

G

gruntlord6OP•9/25/25, 10:35 PM

sometimes wrangler just has transient issues that clear up, I've hit my fair share on "internal error occured" and frozen cli for wrangler deploy that wouldn't work no matter what I did, then they worked fine the next day

G

gruntlord6OP•9/25/25, 10:35 PM

I know its not me because I watch it happen in the CI/CID pipeline in the dashboard as well

P

pandalambda2•9/26/25, 4:47 AM

wrangler just shells out to docker build anyway right?

Ppandalambda2 wrangler just shells out to docker build anyway right?

G

goofysystem•9/26/25, 6:07 AM

Yeah its still using orbstack to build but it still behaves differently from running

docker build

docker build

docker build

docker build. I pretty sure I'm hitting some kind of constraint or something is failing silently.

P

pandalambda2•9/26/25, 8:09 AM

you on the latest wrangler? I've had issues with containers deploy before when I was a few versions behind, but not at the image build stage

Ppandalambda2 you on the latest wrangler? I've had issues with containers deploy before when ...

G

goofysystem•9/26/25, 8:25 AM

omg updating orbstack was the issue. Just downloaded Docker Desktop and it just works lol

Ggoofysystem omg updating orbstack was the issue. Just downloaded Docker Desktop and it just ...

G

gruntlord6OP•9/26/25, 1:46 PM

yea figured that was it

G

gruntlord6OP•9/26/25, 1:47 PM

had similar issues with docker cli vs the full download of docker desktop

W

will smith•9/26/25, 3:02 PM

Anything I'm doing obviously wrong? Just trying to deploy this containers repo: https://github.com/ghostwriternr/claude-code-containers It's not mine, but getting this error in the build on cloudflare
https://dash.cloudflare.com/a3f6e70849e6eb5ca1ebaf6083bc84ba/workers/services/view/claude-code-containers/production/builds/e8a8b77c-ca11-4ddf-8439-a7c204bc4b69

{"url":"https://api.cloudflare.com/client/v4/accounts/a3f6e70849e6eb5ca1ebaf6083bc84ba/cloudchamber/me","status":401,"statusText":"Unauthorized","body":{"error":"Unauthorized: Account is not authorized"},"request":{"method":"GET","url":"/me","errors":{"401":"Unauthorized","500":"There has been an internal error"}},"name":"ApiError"}

{"url":"https://api.cloudflare.com/client/v4/accounts/a3f6e70849e6eb5ca1ebaf6083bc84ba/cloudchamber/me","status":401,"statusText":"Unauthorized","body":{"error":"Unauthorized: Account is not authorized"},"request":{"method":"GET","url":"/me","errors":{"401":"Unauthorized","500":"There has been an internal error"}},"name":"ApiError"}

{"url":"https://api.cloudflare.com/client/v4/accounts/a3f6e70849e6eb5ca1ebaf6083bc84ba/cloudchamber/me","status":401,"statusText":"Unauthorized","body":{"error":"Unauthorized: Account is not authorized"},"request":{"method":"GET","url":"/me","errors":{"401":"Unauthorized","500":"There has been an internal error"}},"name":"ApiError"}

{"url":"https://api.cloudflare.com/client/v4/accounts/a3f6e70849e6eb5ca1ebaf6083bc84ba/cloudchamber/me","status":401,"statusText":"Unauthorized","body":{"error":"Unauthorized: Account is not authorized"},"request":{"method":"GET","url":"/me","errors":{"401":"Unauthorized","500":"There has been an internal error"}},"name":"ApiError"}

ZZnuff Can I use an Container to run ffmpeg to output a video stream as MPEG-TS to simu...

1

1984 Ford Laser•9/27/25, 2:19 AM

Probably, there is an ffmpeg example thats written in rust, but its for generating gifs so you'd need to figure that part out
https://github.com/megaconfidence/wifski/tree/main

S

Shashwat•9/27/25, 12:41 PM

I am trying to use a django built container, with worker's containers, and I am getting an empty body on django end(POST request). Get is working fine (this means that container is running fine). Anything wrong that I might be doing?

C

CodingCoop | Co-Founder Nullshot•9/28/25, 4:41 AM

Wen standard-2 :NotLikeThis:

K

Kirk Ouimet•9/30/25, 12:26 AM

Getting the issue

Container suddenly disconnected, try again

Container suddenly disconnected, try again

Container suddenly disconnected, try again

Container suddenly disconnected, try again - has been working fine for months no changes on our side

K

Kirk Ouimet•9/30/25, 12:42 AM

Confirmed this is happening on fresh deploys of new containers

K

Kirk Ouimet•9/30/25, 12:43 AM

Getting the error "VMStopped"

KKirk Ouimet Getting the issue `Container suddenly disconnected, try again` - has been workin...

K

kian•9/30/25, 12:52 AM

What's your application ID (the UUID in the URL)?

Kkian What's your application ID (the UUID in the URL)?

K

Kirk Ouimet•9/30/25, 12:58 AM

a0325a49-9493-4e83-b6af-287985aed4dd

KKirk Ouimet a0325a49-9493-4e83-b6af-287985aed4dd

K

kian•9/30/25, 1:01 AM

Thanks, we'll take a look. You haven't made any changes / rollouts & it just started failing out of nowhere?

Kkian Thanks, we'll take a look. You haven't made any changes / rollouts & it just sta...

K

Kirk Ouimet•9/30/25, 1:13 AM

Correct - it started failing a couple of days ago. I tried to fix it by changing the container from "standard" to "basic" - no luck. Just switched back from "basic" to "standard" and still same error.

K

kian•9/30/25, 1:35 AM

Is it when you're making a rollout? Are your containers setup to handle the

SIGTERM

SIGTERM

SIGTERM

SIGTERM signal from the rollout?

Kkian Is it when you're making a rollout? Are your containers setup to handle the `SIG...

K

Kirk Ouimet•9/30/25, 5:25 PM

OK @kian I figured it out after lots of trial and error. Something happened on Cloudflares end that is breaking

POST

POST

POST

POST requests from the Workers to the Containers on the first try. It causes this error:

Container suddenly disconnected, try again

Container suddenly disconnected, try again

Container suddenly disconnected, try again

Container suddenly disconnected, try again

So, I implemented retry logic for POST requests that waits 1 second and retries the POST request again and again. It usually works within the second or third request.

GET requests work perfectly every time

My POST retry flow works for now - hope this is helpful

K

Kirk Ouimet•9/30/25, 6:01 PM

And some notes from Claude to the containers team

Screenshot_2025-09-30_at_12.01.22_PM.png

P

Phatso•9/30/25, 7:20 PM

so in the base containers config they simply reference a dockerfile like this: https://github.com/cloudflare/templates/blob/main/containers-template/wrangler.jsonc#L13

that's not ideal for my project because:
1. I want to build the containers myself
- (I need to pass ARGs and then minify them)
2. I want to keep my

docker/

docker/

docker/

docker/ stuff separate of my

web/

web/

web/

web/ stuff

I made this project a few days after Containers came out. Are there any new built-in mechanisms to help me handle this?

Additionally, I need to periodically update my images in the container repo. So far I've been using a Github Action that builds and pushes the new versions using the wrangler CLI
, however this seems like it.. breaks(?) my images? Eventually, after a few updates, when a container boots up it says it can't find the image.

To fix this, I've just had to manually build + minify + push them on my machine.

Any advice would be appreciated!

KKirk Ouimet OK @kian I figured it out after lots of trial and error. Something happened on C...

P

Pranjal•10/1/25, 5:27 AM

I’m experiencing the same issue — everything works as expected in the development environment, but in production I’m getting a

Container suddenly disconnected, try again

Container suddenly disconnected, try again

Container suddenly disconnected, try again

Container suddenly disconnected, try again error with status code 500, even though my container is actually responding with status code 409 or 201. The logs show that the service inside the container returns the correct status code. This issue occurs specifically on POST requests.
Container App ID: a037b631-8b38-4ea3-9ca6-1c094184df54.

A

arnar•10/1/25, 3:30 PM

I'm getting a lot of issues like this

Failed to start container: start() cannot be called on a container that is already running.

Failed to start container: start() cannot be called on a container that is already running.

Failed to start container: start() cannot be called on a container that is already running.

Failed to start container: start() cannot be called on a container that is already running.
I'm using the

getRandom

getRandom

getRandom

getRandom method of selecting a container so some requests might be hitting the same cold container when running requests. But I'm never calling

start()

start()

start()

start() myself, so it seems like an issue in the internal code of the

cloudflare:containers

cloudflare:containers

cloudflare:containers

cloudflare:containers package.

I'm also getting this error fairly frequently

There is no Container instance available at this time.
This is likely because you have reached your max concurrent instance count (set in wrangler config) or are you currently provisioning the Container.
If you are deploying your Container for the first time, check your dashboard to see provisioning status, this may take a few minutes.

There is no Container instance available at this time.
This is likely because you have reached your max concurrent instance count (set in wrangler config) or are you currently provisioning the Container.
If you are deploying your Container for the first time, check your dashboard to see provisioning status, this may take a few minutes.

There is no Container instance available at this time.
This is likely because you have reached your max concurrent instance count (set in wrangler config) or are you currently provisioning the Container.
If you are deploying your Container for the first time, check your dashboard to see provisioning status, this may take a few minutes.

There is no Container instance available at this time.
This is likely because you have reached your max concurrent instance count (set in wrangler config) or are you currently provisioning the Container.
If you are deploying your Container for the first time, check your dashboard to see provisioning status, this may take a few minutes.

Even though there's no rollout going on and I have plenty of available machines (either stopped or started).

Any specific solution to this or just a symptom of it still being in beta?

D

dr.dj•10/1/25, 5:25 PM

Will Containers have access to D1's like Workers?

M

Mike Nomitch•10/1/25, 8:57 PM

Both are planned.

First step -> We're working on generic requests from container to worker on specified hostnames. IE:

foo.cf

foo.cf

foo.cf

foo.cf in the container calls to

handleFoo

handleFoo

handleFoo

handleFoo. - That will open up a bunch of options, and then from there we'll build out more official integrations with D1 and hyperdrive.

R2 also definitely coming, but not as sure on timeline yet. The step above would allow you to manually set it up, but the ideal interface is just a mounted volume IMO.

M

Mike Nomitch•10/1/25, 8:58 PM

Also...

Larger Container Instances are live! - https://developers.cloudflare.com/changelog/2025-10-01-new-container-instance-types/

Get up to 4 vCPU, 12 GiB memory, and 20 GB Disk.

M

Mike Nomitch•10/1/25, 9:02 PM

( next up: pricing update and custom instance types)

I

iddogino•10/2/25, 12:10 AM

@Mike Nomitch | Workers PM love the larger instance types! Using the latest Wrangler it's complaining about the instane types not being valid (still looks for the valu to be

["dev","basic","standard"]

["dev","basic","standard"]

["dev","basic","standard"]

["dev","basic","standard"]) -- is there a canary or something I should be using?

Iiddogino @Mike Nomitch | Workers PM love the larger instance types! Using the latest Wran...

C

Chaika•10/2/25, 12:24 AM

There's a PR for it https://github.com/cloudflare/workers-sdk/pull/10844 and a linked preview but looks like it'll be out pretty soon

CChaika There's a PR for it https://github.com/cloudflare/workers-sdk/pull/10844 and a l...

I

iddogino•10/2/25, 1:13 AM

Awesome, thanks

D

Didac•10/2/25, 7:19 AM

hey guys, I thought I was going crazy but from what I can gather, the Container suddenly disconnected problem is a cloudflare issue? and the only way to workaround it is just to implement a retry logic?

D

Didac•10/2/25, 7:42 AM

i can confirm the retry logic works but it's crazy to have to do that :NotLikeThis:

DDidac hey guys, I thought I was going crazy but from what I can gather, the Container ...

K

kian•10/2/25, 8:41 AM

We're already actively looking into it & have a possible fix on the way.

MMike Nomitch Both are planned. First step -> We're working on generic requests from containe...

K

Karthik Ramani•10/2/25, 9:06 AM

so people in the pro plan can use standard-4 4 12 GiB 20 GB container right? we are trying the vibe SDK which is recently launched, in that it says you need an enterprise plan, please clarify? will they update it?

D

Didac•10/2/25, 10:15 AM

i have a project that i run with react-router dev, is it possible to run containers at the same time with this on the same project, same wrangler config? i tried and i get workerd/jsg/util.c++:320: error: e = kj/async-io-unix.c++:1509: failed: broken.constructorFailed; jsg-internal.Error: connect(): No such file or directory; address = unix:///var/run/docker.sock
stack: 102b17597 102b1540f 102b15a50 10091350c 100c0b747 100c0d05b 100c12d27 1013e96c0 1013e39b4 100931568 100f00c1b 100948f7f 1009232d3 100949e13 10125e57c 101260a7f 100f032cb 1008dfb38 10107302c 100f86538; sentryErrorContext = jsgInternalError; wdErrId = u6uc42g0bpojgvbp9g8mt5h2.

DDidac i have a project that i run with react-router dev, is it possible to run contain...

D

Didac•10/2/25, 10:16 AM

but the container on its own worker project works fine. when running alongside react-router dev, i get that error. docker image does seem to build though but i don't get the "container image(s) ready"

D

Didac•10/2/25, 12:36 PM

Works only with wrangler dev.. it’s alright

Similar Threads