as in the rolling deployments?

G

gruntlord6OP•8/23/25, 3:41 PM

or the actual push to cloudflare

Ggruntlord6 as in the rolling deployments?

T

TobiLG•8/23/25, 4:27 PM

Pre-existing application with updated images…

TTobiLG Pre-existing application with updated images…

G

gruntlord6OP•8/23/25, 4:47 PM

They take a while for me as well, and they are not exactly large images

I

iddogino•8/24/25, 1:21 AM

Experiencing a new issue and wondering if anyone has experienced it too. I have worker A conencting to worker B using a service binding (with

fetch

fetch

fetch

fetch), and worker B uses a container. It used to work (last tested about a week ago), but as of yesterday it doesn't seem to work at all. Worker A makes the fetch request and it just gets stuck.
1. Running both locally with wrangler - everything works as expected (I can see A fetching from B locally).
2. Making a regular request to B works (when I switch to

fetch("https://worker-b.account.workers.dev/process/video"

fetch("https://worker-b.account.workers.dev/process/video"

fetch("https://worker-b.account.workers.dev/process/video"

fetch("https://worker-b.account.workers.dev/process/video" it works fine).

Anyone seeing something similar?

Iiddogino Experiencing a new issue and wondering if anyone has experienced it too. I have ...

D

darkpool•8/24/25, 2:46 AM

does

wrangler tail

wrangler tail

wrangler tail

wrangler tail show any logs?

Ddarkpool does `wrangler tail` show any logs?

I

iddogino•8/24/25, 4:09 PM

I can see the request going out from A but no request makes it to B...

T

TobiLG•8/25/25, 2:15 PM

Has anyone else problems when redeploying container projects? E.g. I see the following errors:

Checking for local image flexstore:6601d7c5 failed with error: Cannot read properties of undefined (reading 'split')

Checking for local image flexstore:6601d7c5 failed with error: Cannot read properties of undefined (reading 'split')

Checking for local image flexstore:6601d7c5 failed with error: Cannot read properties of undefined (reading 'split')

Checking for local image flexstore:6601d7c5 failed with error: Cannot read properties of undefined (reading 'split'). If I delete the containers app in the Dashboard, I can deploy again

T

Tory•8/25/25, 4:26 PM

What would cause container instances to just stop. These instances have been running steadily, without any code changes for several weeks. Then suddenly they all completely died.

D

deved9036•8/25/25, 7:47 PM

are there issues with deploying containers? just stopped working all of a sudden today for me

D

deved9036•8/25/25, 7:48 PM

seems to be mainly containers, also the observability is throwing a bunch of errors all of a sudden

T

TobiLG•8/25/25, 9:34 PM

yeah, same for me. Have you tried updating to the latest wrangler?

D

deved9036•8/25/25, 9:41 PM

i'll give it a god now

D

deved9036•8/25/25, 9:51 PM

okaayy nerverming! seems that fixed it lmao, works on 4.32.0

D

deved9036•8/25/25, 9:52 PM

@TobiLG you still having problem on the latest?

Ddeved9036 @TobiLG you still having problem on the latest?

T

TobiLG•8/25/25, 9:54 PM

not currently, but it was pretty unstable the last few days

D

deved9036•8/25/25, 9:55 PM

yeah, for sure!

J

julian7797•8/25/25, 11:33 PM

When using a container from another durable object, I appear to be running into issues, but from inside regular worker, all is well? Anyone else seen this

D

danamajid•8/26/25, 10:03 AM

hi @Mike Nomitch | Workers PM i'm getting:
"The image registry does not exist"

according to https://www.answeroverflow.com/m/1389977616509047009
you shared it's because the account was part of the private beta (which i my case it was).

can you pls help?

Anyone seen this before when pushing - Cloudflare Developers

Anyone seen this before when pushing their image?

npx wrangler@latest containers images list

 ⛅️ wrangler 4.22.0
───────────────────

Error listing images: ApiError: The image registry does not exist

npx wrangler@latest containers images list

 ⛅️ wrangler 4.22.0
───────────────────

Error listing images: ApiError: The image registry does not exist

npx wrangler@latest containers images list

 ⛅️ wrangler 4.22.0
───────────────────

Error listing images: ApiError: The image registry does not exist

npx wrangler@latest containers images list

 ⛅️ wrangler 4.22.0
───────────────────

Error listing images: ApiError: The image registry does not exist

supposed to be using the built-in registry, maybe I've missed something obvious

Anyone seen this before when pushing - Cloudflare Developers

N

Nicolasmp•8/26/25, 11:57 AM

Hi there! Is there any way to have different

sleepAfter

sleepAfter

sleepAfter

sleepAfter variables according to env variables? For example, I want my container to stop after an hour in dev but never shutdown in prod.

NNicolasmp Hi there! Is there any way to have different `sleepAfter` variables according to...

K

kian•8/26/25, 5:58 PM

I think you can just set it to a

this.env.???

this.env.???

this.env.???

this.env.??? value

K

kian•8/26/25, 5:58 PM

export class MyContainer extends Container {
  defaultPort = 8080;
  sleepAfter = this.env.SLEEP_AFTER;
}

export class MyContainer extends Container {
  defaultPort = 8080;
  sleepAfter = this.env.SLEEP_AFTER;
}

export class MyContainer extends Container {
  defaultPort = 8080;
  sleepAfter = this.env.SLEEP_AFTER;
}

export class MyContainer extends Container {
  defaultPort = 8080;
  sleepAfter = this.env.SLEEP_AFTER;
}

Kkian ```js export class MyContainer extends Container { defaultPort = 8080; sleep...

N

Nicolasmp•8/26/25, 5:59 PM

Alright, and if that variable is undefined it will default to never sleeping?

K

kian•8/26/25, 6:00 PM

The default value is 10 minutes so that

S

Sean•8/26/25, 7:09 PM

Wondering if anyone has some guidance they can share - we have an AI process that runs in a container and takes about 15-20 minutes per invocation. This is triggered by an R2 event subscription where the consumer worker calls my Cloudflare Container app. Right now the issue is the proxy worker that forwards the request to the container is timing out at 180,000 ms (3 minutes) and causing the process to be retried. The actual process works within the deployed container, but we don't want it to be continuously retried by the platform timeout error. This seems to be the worker CPU time limit. Unfortunately pushing it up to 5 minutes won't help.

SSean Wondering if anyone has some guidance they can share - we have an AI process tha...

C

Chaika•8/26/25, 7:21 PM

Cpu time is not consumed by waiting on i/o like a fetch. If the client stays connected, there's no limit on duration. Do they all timeout at exactly 3 minutes? That doesn't really match any platform limit that comes to mind, hmm. I assume you're using a queue and calling the container worker via rpc from the queue consumer?

CChaika Cpu time is not consumed by waiting on i/o like a fetch. If the client stays con...

S

Sean•8/26/25, 7:32 PM

Yes, correct. I have a message worker (queue consumer) that makes a request to my CF Container app. The worker associated with the container app consistently errors out at ~180k ms

SSean Yes, correct. I have a message worker (queue consumer) that makes a request to m...

C

Chaika•8/26/25, 7:35 PM

Queue Consumers should have a max of 15 minutes duration time. Proxy Worker should stay alive as long as the request is pending. The container will sleep if no requests in 10 minutes by default, unless you've configured sleepAfter to 3 minutes.
If you click on the event, is there any more info on the error?

CChaika Queue Consumers should have a max of 15 minutes duration time. Proxy Worker shou...

S

Sean•8/26/25, 7:37 PM

Here's the full error

SSean Here's the full error

C

Chaika•8/26/25, 7:38 PM

That's from the container worker, not the queue consumer

CChaika That's from the container worker, not the queue consumer

S

Sean•8/26/25, 7:39 PM

Correct, that's where I'm getting the errors (the container worker). Apologies if I misstated.

SSean Correct, that's where I'm getting the errors (the container worker). Apologies i...

C

Chaika•8/26/25, 7:45 PM

Your queue consumer should be awaiting the fetch/rpc and then returning success, otherwise it'd just be building up the queue over and over. Are you doing something weird like waitUntil in it and ignoring errors?

S

Sean•8/26/25, 7:53 PM

@Chaika This is my queue consumer code:

Error details attempting to hit the container app start-async endpoint:

Msg 2000d8094472de33684f1967e7365521: Error processing message (attempt 1) for d1cab0d6-be82-4211-a6a9-c53c00dbff40: Error: HTTP error! status: 500 - {"error":"Internal Server Error"}

Msg 2000d8094472de33684f1967e7365521: Error processing message (attempt 1) for d1cab0d6-be82-4211-a6a9-c53c00dbff40: Error: HTTP error! status: 500 - {"error":"Internal Server Error"}

Msg 2000d8094472de33684f1967e7365521: Error processing message (attempt 1) for d1cab0d6-be82-4211-a6a9-c53c00dbff40: Error: HTTP error! status: 500 - {"error":"Internal Server Error"}

Msg 2000d8094472de33684f1967e7365521: Error processing message (attempt 1) for d1cab0d6-be82-4211-a6a9-c53c00dbff40: Error: HTTP error! status: 500 - {"error":"Internal Server Error"}

SSean @Chaika This is my queue consumer code: Error details attempting to hit the co...

C

Chaika•8/26/25, 8:18 PM

hmm, yea I don't think this is a container thing. Your worker log says cancelled, meaning the calling worker gave up on it.
Using a layer inbetween/Mastra Client is going to complicate getting the underlying error out, a quick google search shows there's a configurable timeout for Mastra which a default, worth looking into

CChaika hmm, yea I don't think this is a container thing. Your worker log says cancelled...

S

Sean•8/26/25, 8:19 PM

Ok thanks for your help

D

Dipan•8/27/25, 1:31 AM

Hey, I am deploying a Server in cloudflare container, deployed it successfully and get this response -

Total Upload: 53.47 KiB / gzip: 13.58 KiB
Worker Startup Time: 14 ms
Your worker has access to the following bindings:
- Durable Objects:
  - MORPH_CONTAINER: MorphContainer
- Vars:
  - NODE_ENV: "production"
Uploaded morph-server (9.65 sec)
Deployed morph-server triggers (1.76 sec)

Total Upload: 53.47 KiB / gzip: 13.58 KiB
Worker Startup Time: 14 ms
Your worker has access to the following bindings:
- Durable Objects:
  - MORPH_CONTAINER: MorphContainer
- Vars:
  - NODE_ENV: "production"
Uploaded morph-server (9.65 sec)
Deployed morph-server triggers (1.76 sec)

Total Upload: 53.47 KiB / gzip: 13.58 KiB
Worker Startup Time: 14 ms
Your worker has access to the following bindings:
- Durable Objects:
  - MORPH_CONTAINER: MorphContainer
- Vars:
  - NODE_ENV: "production"
Uploaded morph-server (9.65 sec)
Deployed morph-server triggers (1.76 sec)

Total Upload: 53.47 KiB / gzip: 13.58 KiB
Worker Startup Time: 14 ms
Your worker has access to the following bindings:
- Durable Objects:
  - MORPH_CONTAINER: MorphContainer
- Vars:
  - NODE_ENV: "production"
Uploaded morph-server (9.65 sec)
Deployed morph-server triggers (1.76 sec)

But when I am seng a request to the server getting this error (attached in screenshot)

D

Dipan•8/27/25, 1:31 AM

Can anyone help me here?

DDipan Hey, I am deploying a Server in cloudflare container, deployed it successfully a...

I

Isaac McFadyen•8/27/25, 1:33 AM

How are you calling the container? Sounds like your Worker code is throwing the error before the request makes it to the container.

D

Dipan•8/27/25, 1:34 AM

This is the workser/index.js file

message.txt2.04KB

D

Dipan•8/27/25, 1:36 AM

worker/index.js*

IIsaac McFadyen How are you calling the container? Sounds like your Worker code is throwing the ...

D

Dipan•8/27/25, 1:39 AM

Can you send me any resources, Where I can see that how can I make a ideal worker?

A

A Shy Cow•8/27/25, 10:36 AM

hi everyone

is there any containers cost calculator? i need a container which is up 24/7 and i'd like to know how much i would pay for it

A

Alexander•8/27/25, 12:31 PM

I am trying to run a dev server and point wrangler to pull an image from cloudflare registry but run into an error - anyone know how to solve?

∷ Building container images for local development...
                                                                                                                                                                                                                                                  
error when starting dev server:
TypeError: Failed to parse URL from /registries/registry.cloudflare.com/credentials                                                                                                                                                                
    at node:internal/deps/undici/undici:13510:13                                                                                                                                                                                                   
    at async sendRequest (file:///home/azuev/polymer/node_modules/.pnpm/@cloudflare+vite-plugin@1.12.0_vite@7.1.3_@types+node@24.3.0_jiti@2.5.1_lightningcss@1._8b43f7dcedb891a211abe2294734dcbb/node_modules/@cloudflare/vite-plugin/dist/index.js:14260:10)                                                                                                                                                                                                                                         
    at async file:///home/azuev/polymer/node_modules/.pnpm/@cloudflare+vite-plugin@1.12.0_vite@7.1.3_@types+node@24.3.0_jiti@2.5.1_lightningcss@1._8b43f7dcedb891a211abe2294734dcbb/node_modules/@cloudflare/vite-plugin/dist/index.js:14320:26    
 ELIFECYCLE  Command failed with exit code 1.
➜  polymer git:(main) ✗

∷ Building container images for local development...
                                                                                                                                                                                                                                                  
error when starting dev server:
TypeError: Failed to parse URL from /registries/registry.cloudflare.com/credentials                                                                                                                                                                
    at node:internal/deps/undici/undici:13510:13                                                                                                                                                                                                   
    at async sendRequest (file:///home/azuev/polymer/node_modules/.pnpm/@cloudflare+vite-plugin@1.12.0_vite@7.1.3_@types+node@24.3.0_jiti@2.5.1_lightningcss@1._8b43f7dcedb891a211abe2294734dcbb/node_modules/@cloudflare/vite-plugin/dist/index.js:14260:10)                                                                                                                                                                                                                                         
    at async file:///home/azuev/polymer/node_modules/.pnpm/@cloudflare+vite-plugin@1.12.0_vite@7.1.3_@types+node@24.3.0_jiti@2.5.1_lightningcss@1._8b43f7dcedb891a211abe2294734dcbb/node_modules/@cloudflare/vite-plugin/dist/index.js:14320:26    
 ELIFECYCLE  Command failed with exit code 1.
➜  polymer git:(main) ✗

∷ Building container images for local development...
                                                                                                                                                                                                                                                  
error when starting dev server:
TypeError: Failed to parse URL from /registries/registry.cloudflare.com/credentials                                                                                                                                                                
    at node:internal/deps/undici/undici:13510:13                                                                                                                                                                                                   
    at async sendRequest (file:///home/azuev/polymer/node_modules/.pnpm/@cloudflare+vite-plugin@1.12.0_vite@7.1.3_@types+node@24.3.0_jiti@2.5.1_lightningcss@1._8b43f7dcedb891a211abe2294734dcbb/node_modules/@cloudflare/vite-plugin/dist/index.js:14260:10)                                                                                                                                                                                                                                         
    at async file:///home/azuev/polymer/node_modules/.pnpm/@cloudflare+vite-plugin@1.12.0_vite@7.1.3_@types+node@24.3.0_jiti@2.5.1_lightningcss@1._8b43f7dcedb891a211abe2294734dcbb/node_modules/@cloudflare/vite-plugin/dist/index.js:14320:26    
 ELIFECYCLE  Command failed with exit code 1.
➜  polymer git:(main) ✗

∷ Building container images for local development...
                                                                                                                                                                                                                                                  
error when starting dev server:
TypeError: Failed to parse URL from /registries/registry.cloudflare.com/credentials                                                                                                                                                                
    at node:internal/deps/undici/undici:13510:13                                                                                                                                                                                                   
    at async sendRequest (file:///home/azuev/polymer/node_modules/.pnpm/@cloudflare+vite-plugin@1.12.0_vite@7.1.3_@types+node@24.3.0_jiti@2.5.1_lightningcss@1._8b43f7dcedb891a211abe2294734dcbb/node_modules/@cloudflare/vite-plugin/dist/index.js:14260:10)                                                                                                                                                                                                                                         
    at async file:///home/azuev/polymer/node_modules/.pnpm/@cloudflare+vite-plugin@1.12.0_vite@7.1.3_@types+node@24.3.0_jiti@2.5.1_lightningcss@1._8b43f7dcedb891a211abe2294734dcbb/node_modules/@cloudflare/vite-plugin/dist/index.js:14320:26    
 ELIFECYCLE  Command failed with exit code 1.
➜  polymer git:(main) ✗

Curiously I have successfully built and pushed an image - so I am not sure what is the issue?

A

Alexander•8/27/25, 1:26 PM

Another thing I've noticed (hesitant to call it an issue) but calling .getState() returns stale values if:
- in development I manually stop the docker container instance OR ctrl +c the dev server
- impact: when I try to call / fetch container next time, I check via .getState() which returns a stale value (whatever the state was before instance was manually stopped)

I would have thought that .getState() always returns a fresh state but without booting the container up / waiting for ports. Am I wrong?

I previously stored state flag (i.e. running / healthy / error) in DO KV storage using lifecycle hooks but ran into the same stale values issue.

Am I missing something?

SSean Wondering if anyone has some guidance they can share - we have an AI process tha...

S

sampotter•8/28/25, 2:47 AM

I've had this issue for a while. In my limited understanding from testing it looks like container lifecycles are tied to durable objects. If the durable object is evicted from memory, the container is killed also. I have never been able to keep a durable object alive for more than 180,000ms. It looks like that is some sort of hard limit on DOs.

S

sampotter•8/28/25, 2:48 AM

Started a thread here that never got anywhere containers-beta

S

sampotter•8/28/25, 2:50 AM

Our solution in the interim is to make the container workload durable to restarts (which doesn't sound like it's possible for your workload). We also run a loop within the durable object to automatically awake it after it is evicted.

M

mike•8/28/25, 9:53 PM

are other folks still hitting this as well? it continues to be a pain point for us deploying changes - containers-beta

Mmike are other folks still hitting this as well? it continues to be a pain point for ...

K

kian•8/28/25, 9:59 PM

Is

(request id: undefined):  Internal Server Error

(request id: undefined): Internal Server Error

(request id: undefined):  Internal Server Error

(request id: undefined): Internal Server Error the exact error you're getting?

Kkian Is `(request id: undefined): Internal Server Error` the exact error you're gett...

M

mike•8/28/25, 10:02 PM

yes, just after the edit to update the image:

Error rolling out application <app> due to an internal error (request id: undefined):   Internal Server Error

Error rolling out application <app> due to an internal error (request id: undefined): Internal Server Error

Error rolling out application <app> due to an internal error (request id: undefined):   Internal Server Error

Error rolling out application <app> due to an internal error (request id: undefined): Internal Server Error

K

kian•8/28/25, 10:06 PM

What's the application ID (UUID in the dashboard URL when viewing a Containers app)?

Similar Threads

Similar Threads

Similar Threads