there is a probleme for deploy containers. i have already deploy a new version but it always display

there is a probleme for deploy containers. i have already deploy a new version but it always display updating for a long time

taoOP•10/29/25, 2:41 PM

Ttao there is a probleme for deploy containers. i have already deploy a new version b...

<@235148962103951360>•10/29/25, 4:26 PM

It seemed to finish updating after some number of hours when I had the same issue.

<@235148962103951360>•10/29/25, 4:27 PM

We need to be able to choose where the container starts

Paul•10/29/25, 7:31 PM

Maybe I need to delete the durable object instance that is associated with the container instance to delete it? Can someone from Cloudflare please provide guidance here

PPaul Maybe I need to delete the durable object instance that is associated with the c...

1984 Ford Laser•10/29/25, 7:46 PM

I was under the impression that when the container says inactive that means its resources are no longer being held onto? In the same way a DO gets evicted

<<@235148962103951360>We need to be able to choose where the container starts

taoOP•10/29/25, 10:12 PM

yeah i wait almost 1h it finished.

taoOP•10/29/25, 10:45 PM

The issue has reappeared — the containers are stuck in “updating.” Is there any solution besides just waiting?

nicoritschel•10/30/25, 3:03 AM

FYI seems this might just be a UI issue as you probably will see your container versions incrementing

Ttao yeah i wait almost 1h it finished.

<@235148962103951360>•10/30/25, 5:19 AM

i had to wait like 6 hourw probably for mine

PPaul Maybe I need to delete the durable object instance that is associated with the c...

<@235148962103951360>•10/30/25, 5:20 AM

Seems as though theres not much support here.

<@235148962103951360>•10/30/25, 5:20 AM

support is yet to respond to my concerning billing inquiry

<@235148962103951360>•10/30/25, 5:21 AM

and it has been over a month with no response and bizzare cpu time and requests that dont show up on any of my workers

<@235148962103951360>•10/30/25, 5:21 AM

no explanation at all

<@235148962103951360>•10/30/25, 5:21 AM

extremely disappointing from such a large corporation to not respond or give an explanation.

<@235148962103951360>•10/30/25, 5:22 AM

My company is losing trust in cloudflare after that

<<@235148962103951360>Seems as though theres not much support here.

Isaac McFadyen•10/30/25, 5:24 AM

?discord-support

SuperHelpflare•10/30/25, 5:24 AM

This Discord is not an official support form. The Community Champions, community members and employees are here because they want to be not because they need to be.
Please do not ping Community Champions or employees for support reasons.

You can open a ticket on the Support Portal if you want official support.

IIsaac McFadyen ?discord-support

<@235148962103951360>•10/30/25, 5:24 AM

I have made a ticket and there has been no response since september

<@235148962103951360>•10/30/25, 5:25 AM

it is made on the cloudflare website

<@235148962103951360>•10/30/25, 5:25 AM

the last time i brought it up here, someome mentioned the same message, but it is open on the support portal. i mentioned that previously

<@235148962103951360>•10/30/25, 5:26 AM

no emails, nothing

Nnicoritschel FYI seems this might just be a UI issue as you probably will see your container ...

taoOP•10/30/25, 8:04 AM

no, container versions not incrementing

fare•10/30/25, 9:34 AM

Can someone tell me if I'm sending 4-5 requests in a container's URL in a loop, will they all get directed to a single container instance, or they will be distributed against 3-4 instances? How is this derived?

fare•10/30/25, 9:35 AM

Locally I have seen them create multiple instances

kian•10/30/25, 1:53 PM

Depends how you're acquiring them - it's the same as Durable Objects. You can send them all to a static ID for a singleton, you can randomly distribute it across instances, etc

kian•10/30/25, 2:02 PM

https://github.com/cloudflare/templates/blob/36f193b322af58da4366becdae40936410ebda68/containers-template/src/index.ts#L44-L68

Ttao no, container versions not incrementing😳

nicoritschel•10/30/25, 2:07 PM

Yeah mine too sadly

Kkian Depends how you're acquiring them - it's the same as Durable Objects. You can se...

taoOP•10/30/25, 3:19 PM

async fetch(request: Request, env: Env): Promise<Response> {
    // note: "getRandom" to be replaced with latency-aware routing in the near future
    try {
      const instanceNumber = env.WORKER_ENV === 'production' ? 2 : 1;
      const containerInstance = await getRandom(
        env.API_CONTAINER,
        instanceNumber,
      );
      const rs = await containerInstance.fetch(request);
      return rs;
    } catch (error) {
      // Surface failures cleanly in Cloudflare's logs before bubbling up
      console.error('[CloudflareContainer] fetch failed', {
        url: request.url,
        method: request.method,
        message: error instanceof Error ? error.message : String(error),
        stack: error instanceof Error ? error.stack : undefined,
      });
      throw error instanceof Error ? error : new Error(String(error));
    }
  },

async fetch(request: Request, env: Env): Promise<Response> {
    // note: "getRandom" to be replaced with latency-aware routing in the near future
    try {
      const instanceNumber = env.WORKER_ENV === 'production' ? 2 : 1;
      const containerInstance = await getRandom(
        env.API_CONTAINER,
        instanceNumber,
      );
      const rs = await containerInstance.fetch(request);
      return rs;
    } catch (error) {
      // Surface failures cleanly in Cloudflare's logs before bubbling up
      console.error('[CloudflareContainer] fetch failed', {
        url: request.url,
        method: request.method,
        message: error instanceof Error ? error.message : String(error),
        stack: error instanceof Error ? error.stack : undefined,
      });
      throw error instanceof Error ? error : new Error(String(error));
    }
  },

This is my code — I am not using a static ID. If I switch to using a static ID, does that mean my container rollout time won’t be as long?

kian•10/30/25, 3:40 PM

Rollouts depend on how quickly your old Containers are shutting down (they should handle SIGTERM signals) & how quickly the new ones can start

<@235148962103951360>•10/30/25, 4:01 PM

Is there any way to set the location a container starts in?

taoOP•10/30/25, 8:07 PM

If the old containers stay active and never shut down, does that mean I won’t be able to deploy new containers?

taoOP•10/30/25, 8:26 PM

5h for updating....that's strange

Kkian Rollouts depend on how quickly your old Containers are shutting down (they shoul...

taoOP•10/30/25, 8:35 PM

If you were the user, would you accept waiting 5 hours for a new version to be redeployed? What if there’s a hot fix that needs to go live immediately? I’d like to know what we can do to reduce rollout time?

kian•10/30/25, 8:35 PM

Give us an application ID to investigate? It’s not normal behaviour but there’s no IDs for us to look at so far.

Kkian Give us an application ID to investigate? It’s not normal behaviour but there’s ...

taoOP•10/30/25, 8:37 PM

yes ofc. but how to view the appliaction ID

Kkian Give us an application ID to investigate? It’s not normal behaviour but there’s ...

taoOP•10/30/25, 8:39 PM

Application ID: a0351ab5-04ef-428b-9e03-0f45fc78fd25

kian•10/30/25, 8:45 PM

We’ll take a look - there’s a known bug that a new instance we’re trying to bring up can get stuck & we’re not correctly replacing it

taoOP•10/30/25, 8:53 PM

Thank you very much — I really appreciate you looking into this.
Hoping the fix can be rolled out as soon as possible.

kian•10/30/25, 8:54 PM

Generally we expect rollouts to take as long as old instances shutting down and starting new ones - new ones can sometimes get stuck and we need to fix some things to make sure the stuck ones are retried

kian•10/30/25, 8:54 PM

The rollout strategy options right now are only “proceed to the next step once X% of instances are on the new version” but we’ll bring more options over time

Kkian We’ll take a look - there’s a known bug that a new instance we’re trying to brin...

taoOP•10/31/25, 2:42 AM

could you please let us know when the fix is expected to be completed?
Currently each deployment takes a long time and it’s causing impact.

taoOP•10/31/25, 3:43 AM

We’re currently unable to deploy a new version because it’s stuck in the updating state

<@235148962103951360>•10/31/25, 3:43 AM

Can the location of a container be set manually?

Jadugar_Jaggu•10/31/25, 7:39 AM

Cloudflare should remove egress to its own products like kv and r2 from a cloudflare container.

Its preventing me to use it for a real world purpose.

Good for toying.

JJadugar_Jaggu Cloudflare should remove egress to its own products like kv and r2 from a cloudf...

1984 Ford Laser•10/31/25, 7:44 AM

They've said that they plan on doing this in the future. I imagine that will happen when they have bindings within the container

<<@235148962103951360>Can the location of a container be set manually?

1984 Ford Laser•10/31/25, 7:48 AM

Nah

<@235148962103951360>•10/31/25, 10:19 AM

Well that sucks. It would be great to be able to choose the location.

taoOP•10/31/25, 10:26 AM

And I also noticed another issue — even when the status is still updating and the container version hasn’t increased, new containers still start and run.
This is quite confusing, because it’s hard to tell whether my new version has actually been deployed successfully or not.

<<@235148962103951360>Can the location of a container be set manually?

John Spurlock•10/31/25, 4:21 PM

yes, you can constrain a container to run in a given city (EWR etc) or region (ENAM etc)

async fetch(request: Request, env: Env): Promise<Response> { // note: "getRandom" to be replaced with latency-aware routing in the near future try { const instanceNumber = env.WORKER_ENV === 'production' ? 2 : 1; const containerInstance = await getRandom( env.API_CONTAINER, instanceNumber, ); const rs = await containerInstance.fetch(request); return rs; } catch (error) { // Surface failures cleanly in Cloudflare's logs before bubbling up console.error('[CloudflareContainer] fetch failed', { url: request.url, method: request.method, message: error instanceof Error ? error.message : String(error), stack: error instanceof Error ? error.stack : undefined, }); throw error instanceof Error ? error : new Error(String(error)); } },

there is a probleme for deploy containers. i have already deploy a new version but it always display

Similar Threads

Similar Threads

Similar Threads