Cloudflare Developers

CD

Cloudflare Developers

Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news

Join

Containers are available in public beta ...

Hi all, how to overcome "Unauthorized" error during wrangler deploy? I've used deploy to cloudflare with hello-containers template from here https://blog.cloudflare.com/containers-are-available-in-public-beta-for-simple-global-and-programmable/...
No description

Is there any plan of GPU support?

Is there any plan of GPU support?

Should I configure a separate container

Should I configure a separate container per environment (staging vs production) in my wrangler.jsonc? Injected env variables would be different depending on the environment but the image itself will be the same.

Container + R2 + Worker workflow is not

Container + R2 + Worker workflow is not ideal: I am using a separate container service to upload a PDF with a QR code to a remote R2 using the S3 API. My Worker accesses the uploaded PDF from R2 and emails it to the user. This works fine in staging and production but not in development, since the Worker uses a local R2 instance instead of the remote one. I can't use wrangler dev --remote because I use Durable Objects, Workflows, and Queues. Is there any workaround for this?

have anyone gotten "there is no

have anyone gotten "there is no container instance that can be provided to this durable object" after deployed?

Hey team, was wondering if it was

Hey team, was wondering if it was possible to increase the 2gb image size limit for containers? Would ideally like for it to be 10GB

Containers are pretty unusable for us at

Containers are pretty unusable for us at the moment. We get a combination of failures on the majority of requests because instances are inactive (even though we removed the sleepAfter time we had defined (using latest @Cloudflare/containers 0.0.16). We get a combination of A call to blockConcurrencyWhile() in a Durable Object waited for too long. The call was canceled and the Durable Object was reset. errors and this error with 5 instances sitting inactive:
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.
...

I'm trying to deploy a Cloudflare

I'm trying to deploy a Cloudflare container. It works occasionally, but most of the time I encounter the following error: {"error":"Internal server error","message":"A call to blockConcurrencyWhile() in a Durable Object waited for too long. The call was canceled and the Durable Object was reset."} Has anyone come across this issue before or have any reference on how to fix it?...

I've encountered an inconsistency with

I've encountered an inconsistency with how wrangler dev and wrangler deploy handle Docker build contexts. The Issue: When I place my Dockerfile in a subdirectory (e.g., cf-worker/containers/project-a/Dockerfile) and set the image field in wrangler.jsonc to './containers/project-a/Dockerfile': wrangler dev builds successfully...

@Mike Nomitch can you guys create a

@Mike Nomitch | Workers PM can you guys create a containers-help and a bugs channel?

When running Containers locally on macOS

When running Containers locally on macOS, fetch()ing to the Container throws a Container port not found error even after a while the Container has this.ctx.container!.start()ed, which is causing startAndWaitForPorts() to time out. Is it just me or are there any workaround, or is it a known bug? I'm using the latest template from Cloudflare....

can we connect to the hyperdrive using

can we connect to the hyperdrive using containers?

I have a doubt about cloudflare

I have a doubt about cloudflare containers. I have a video processing work load which downlaod the video from r2 and do some processing and send the results to database. Is there any time restrictions for container run time? because it probably take more time depend upon the video size. I think container should call from worker and worker have a time execution limit.

Containers have some sort of

Containers have some sort of simultaneous open connection limits like Workers do?

does that mean that there must be a http

does that mean that there must be a http based entry point for containers to work ?

Is there a way to access/upload to local

Is there a way to access/upload to local R2 from my container or do I have to run wrangler dev --remote to work with workers + containers + r2? I'm using S3 API to interact with R2 from my container.

would be great if we could define memory

would be great if we could define memory/cpu at runtime. i have a few async job flows i deploy via cloudrun, examples are generating videos or zip files, and the amount of memory/disk space is relative to number of input files. atm i use up to 8 vcpu/16gb, so probably awhile before containers is usable as a product

Are containers supported in multi config

Are containers supported in multi config development (wrangler dev -c package/a -c package/b) ? Currently geting container image path resolving issues when running the dev command from root repository.
The image "./Dockerfile" does not appear to be a valid path to a Dockerfile
The image "./Dockerfile" does not appear to be a valid path to a Dockerfile
...

Has anyone solved this kind of error yet

Has anyone solved this kind of error yet? Would love ideas on what to try to get it working.

I'm having an issue with container

I'm having an issue with container configuration where instance_type setting isn't working: ```json "containers": [ {...