Yeah thought I would give cloudflare a try, since all of my applications are already running in k8s,

Yeah thought I would give cloudflare a try, since all of my applications are already running in k8s, but this platform is totally bad. I've set everything up the right way, set my env variables etc. and my applications won't start. Idk why they won't, because you can't even debug it the right way, even with enabled observability

JJ1mb0 Hi, I've got some issues when starting my Go service. I always get this error me...

J1mb0OP•11/5/25, 5:10 PM

No one knows, what could caused this and the shittyy observability tools won't help you

J1mb0OP•11/5/25, 5:11 PM

This platform is so bad.... I'll contact my cc provider and get my money back

JJ1mb0 Yeah thought I would give cloudflare a try, since all of my applications are alr...

gruntlord6•11/5/25, 5:55 PM

well, would you like to try and get it working? or did you just want to fire up a beta product and quit immediately after sinking time into it

Ggruntlord6 well, would you like to try and get it working? or did you just want to fire up ...

J1mb0OP•11/5/25, 5:56 PM

I'm interested to get it to work

gruntlord6•11/5/25, 5:56 PM

so help us help you, what is the issue? are you getting errors? is it not deploying etc

J1mb0OP•11/5/25, 5:58 PM

Yes sure. It is deploying and I'm getting this issue:

DataCloneError: Could not serialize object of type "DurableObjectNamespace". This type does not support serialization.DataCloneError: Could not serialize object of type "DurableObjectNamespace". This type does not support serialization.

J1mb0OP•11/5/25, 5:59 PM

Thats my index.ts

message.txt4.62KB

Ggruntlord6 so help us help you, what is the issue? are you getting errors? is it not deploy...

J1mb0OP•11/5/25, 6:02 PM

Do you need something else?

gruntlord6•11/5/25, 6:08 PM

I think the error is kind of self explanatory isn't it? you are trying to serialize and pass that when it can't be serialized

Ggruntlord6 I think the error is kind of self explanatory isn't it? you are trying to serial...

J1mb0OP•11/5/25, 6:12 PM

Indeed it is and I think it comes from:

   await container.startAndWaitForPorts({
          ports: [8080],
                
          startOptions: {
            enableInternet: true,
            ...c.env, 
          },
        });

   await container.startAndWaitForPorts({
          ports: [8080],
                
          startOptions: {
            enableInternet: true,
            ...c.env, 
          },
        });

`

But If I remove this line, I'm getting the following error:

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

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

J1mb0OP•11/5/25, 6:14 PM

I only see this error in my logs and nothing else. And this application is already running in a k8s cluster without any issues

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

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

gruntlord6•11/5/25, 6:50 PM

I don't use hono or most of your stack so I'm not really going to be much help there.

For starting and stopping the containers, I'd use one of the examples in the documentation as a reference. Right now I have a simple concept express app for backing up durable objects to r2 that gets started by a worker calling the containers durable object. My code was made by referencing one of the examples

J1mb0OP•11/5/25, 6:53 PM

I used the template ...

Brett Willis•11/5/25, 11:45 PM

Got some questions about how the image registry works when specifying the image as a registry tag rather than a Dockerfile:
1. If I push a new version of an image with the same tag, will the container instances update to the new version automatically? Or do I re-deploy the durable object (with no changes)? Or do I need to push to a new tag every time and re-deploy the durable object with the new image tag?
2. If I delete an image from the registry that is still used as the active image for a container, will it cause issues when the container needs to restart?

tao•11/6/25, 7:46 AM

Is there a way to manually trigger a redeployment of a Cloudflare Container from the web dashboard?
Our service went down unexpectedly, and we were only able to recover it by manually redeploying via Wrangler.

Brett Willis•11/6/25, 9:24 AM

Also what's up with logging from containers? When logging JSON with

console.log({ message: 'Some message' })

console.log({ message: 'Some message' })

, the output is pretty-printed and observability treats each line as a separate log, e.g.
-

"message": "{"

"message": "{"

"message": "message: 'Some message'"

"message": "message: 'Some message'"

"message": "}"

"message": "}"

If I make it not pretty-print, then observability doesn't pick up the structured JSON, it just treats it as a normal string, e.g.
-

"message": "{ message: 'Some message' }"

"message": "{ message: 'Some message' }"

And interestingly, writing to stdout with

process.stdout.write(JSON.stringify({ message: 'Some message' }))

process.stdout.write(JSON.stringify({ message: 'Some message' }))

doesn't seem to emit any observability logs at all?? Am I doing something wrong?

tao•11/6/25, 9:53 AM

Our server seems to have gone down again. The health check endpoint stopped responding for an extended period, and there were no error logs displayed on the dashboard. After redeploying a new version, we started seeing error 1101.

tao•11/6/25, 10:03 AM

After switching to another deployed version, the service started working normally again.

tao•11/6/25, 7:05 PM

why there is a error: Network connection lost

sampotter•11/7/25, 12:52 AM

What's the easiest way to disable the container sleep timeout? Or if that's not possible is there a method to guarantee the container will restart?

Ssampotter What's the easiest way to disable the container sleep timeout? Or if that's not ...

1984 Ford Laser•11/7/25, 1:26 AM

You could

stop()

stop()

(or

destroy()

destroy()

) then

start()

start()

it again?

Elia•11/7/25, 3:24 AM

Quick feedback: my containers crash when using

startAndWaitForPorts

startAndWaitForPorts

Works fine on local but immediately crashes on CF infra without any logs / infos

Works without (by just getting and sending requests to it) though

tao•11/7/25, 8:38 AM

We’re frequently encountering network connection lost errors in our application.
Could someone please help investigate or provide guidance on resolving this issue?

tao•11/7/25, 8:47 AM

EElia Quick feedback: my containers crash when using `startAndWaitForPorts` Works fin...

Elia•11/7/25, 12:36 PM

Another thing, think it'd be great if there's an easy way to extend the sleepTime from inside the container

We solved it by having the container invoke the API pinging the container (causing a reset) -- but an internal API would be far more elegant imo

Alex Dahl•11/8/25, 6:44 PM

Any news of persistent disk for containers? Would love to switch over from fly.io, but the lack of persistent disk is a blocker

AAlex Dahl Any news of persistent disk for containers? Would love to switch over from fly.i...

gruntlord6•11/9/25, 4:29 PM

yea a bit of a bummer, you can store data in R2 but then you would have to retrieve it each time before it could be used

Ggruntlord6 yea a bit of a bummer, you can store data in R2 but then you would have to retri...

Alex Dahl•11/10/25, 8:54 AM

Yeah! If containers were colocated with R2 this would have been fine, but that doesn't seem to be the case, i did some benchmarking here:
containers-beta

Justy•11/12/25, 10:54 PM

Hi everyone, just getting started on CF infrastructure and was hoping someone could help:
I have a FastAPI instance running in a container that I'd like to interact with MongoDB, but I'm struggling to find a way to route all egress through a set IP range that I can whitelist in Mongo. Is this possible yet? We are not on an enterprise plan, and likely won't ever be - I've combed the docs for a while now and haven't been able to find anything. Any help would be much appreciated!

JJusty Hi everyone, just getting started on CF infrastructure and was hoping someone co...

1984 Ford Laser•11/12/25, 10:55 PM

Cloudflare uses the same set of IPs across all applications for egress, you can whitelist the following IPs: https://www.cloudflare.com/en-au/ips/

Justy•11/12/25, 11:01 PM

Is the standard way everyone does it in production? Just feels like it wouldn't be the optimal way to secure the connection... essentially be allowing all apps hosted on Cloudflare potential access to our Atlas instance? I'm still relatively new to backend dev, so I could be completely wrong, just want to make sure we're as secure as possible.

11984 Ford Laser Cloudflare uses the same set of IPs across all applications for egress, you can ...

PhoenixSpace•11/12/25, 11:10 PM

Containers don't egress from these IPs iirc

PhoenixSpace•11/12/25, 11:10 PM

containers-beta

JJusty Is the standard way everyone does it in production? Just feels like it wouldn't ...

PhoenixSpace•11/12/25, 11:12 PM

Depending on how the application is set up, you can either use the MongoDB Atlas Admin API to whitelist the container's specific IP address on startup (if its longer lived applications where that won't be happening very frequently), or proxy it through a VPS with a fixed IP address

PhoenixSpace•11/12/25, 11:12 PM

The second is very straightforward to do with Cloudflare infrastructure

Justy•11/12/25, 11:17 PM

Okay awesome thanks, I will look into those options

PPhoenixSpace Containers don't egress from these IPs iirc

1984 Ford Laser•11/13/25, 1:03 AM

huh TIL

11984 Ford Laser Cloudflare uses the same set of IPs across all applications for egress, you can ...

Chaika•11/13/25, 1:42 AM

It's mostly just CDN/workers fetch at this point that goes through them.
TCP Connect/TCP out of Workers use WARP IPs which aren't in that list too (as well as WARP itself)

Paul•11/13/25, 2:53 AM

@cloudflare-container-team, can you confirm this issue?

Fix Cloudflare Container Instance Type Error

Problem: Used invalid instance type "standard-1" which doesn't exist in Cloudflare API.

Error Message:
Expected "containers.instance_type" field to be one of ["dev","basic","standard"] but got "standard-1".

---
Root Cause

Mismatch between documentation and reality:
- Documentation shows: "lite", "standard-1", "standard-2", "standard-3", "standard-4"
- API actually accepts: "dev", "basic", "standard" (only 3 types)

The larger instance types ("standard-1" through "standard-4") are documented but not yet implemented in the Cloudflare Containers public beta.

---
Currently Valid Instance Types

Based on the API validation error, only these 3 types exist:

| Instance Type | Resources (estimated) |
|---------------|-----------------------------------------|
| "dev" | Minimal (likely ~2 GB disk) |
| "basic" | Small (4 GB disk) |
| "standard" | Medium (8 GB disk, 4 GiB RAM, 1/2 vCPU) |

---

PPaul @cloudflare-container-team, can you confirm this issue? Fix Cloudflare Contai...

Paul•11/13/25, 2:54 AM

The website says use 'standard-1': https://developers.cloudflare.com/containers/platform-details/limits/

But wrangler doesn't accept this.

Cloudflare Docs

Limits and Instance Types

The memory, vCPU, and disk space for Containers are set through predefined instance types.
Six instance types are currently available:

Paul•11/13/25, 2:55 AM

wrangler 4.29.1 (update available 4.47.0)
─────────────────────────────────────────────
✘ [ERROR] Processing wrangler.toml configuration:
- Expected "containers.instance_type" field to be one of ["dev","basic","standard"] but got "standard-1".

Logs were written to "/home/runner/.config/.wrangler/logs/wrangler-2025-11-13_02-38-01_715.log"
Error: The process '/opt/hostedtoolcache/node/20.19.5/x64/bin/npx' failed with exit code 1
Error:

Action failed

PPaul ⛅️ wrangler 4.29.1 (update available 4.47.0) ─────────────────────────────────...

Chaika•11/13/25, 3:00 AM

Upgrade to latest wrangler (or past 4.41.0 when they were added)

Paul•11/13/25, 3:01 AM

Ok I'm using a Github Action: cloudflare/wrangler-action@v3

Let me see if I can somehow force the updgrade after the action installs it's version of wrangler...

PPaul Ok I'm using a Github Action: cloudflare/wrangler-action@v3 Let me see if I can...

Isaac McFadyen•11/13/25, 3:05 AM

You should specify that in the Action config, don't try to manually upgrade it after:
https://github.com/cloudflare/wrangler-action?tab=readme-ov-file#configuration

Jadugar_Jaggu•11/13/25, 4:59 AM

Hey facing container issues from last 6-7 hours. I just checked the dashboard and it showing this container has no instances. It was working fine from past 30 days.

Jadugar_Jaggu•11/13/25, 5:00 AM

Is there any global issue in containers?

Abdxlahs•11/13/25, 11:56 AM

Have anyone deployed n8n on containers?

AAbdxlahs Have anyone deployed n8n on containers?

Paul•11/13/25, 4:09 PM

No, but actually have had this though - let us know if you do it!

AAbdxlahs Have anyone deployed n8n on containers?

xvvvyz•11/13/25, 4:13 PM

wouldn't you need persistent storage?

Yeah thought I would give cloudflare a try, since all of my applications are already running in k8s,

Similar Threads

Similar Threads

Similar Threads