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:
5 Replies
Hey @Tory going to update the channel, but we actually needed to land a different change for
sleepAfter to properly work - the 0.0.14-16 changes were for some other minor issues.
If you use 0.0.10, it should fix sleepAfter at least
Containers are pretty unusable for us at the moment
Sorry about this - we're working thru the main things - more friction than we want at this point obviously 😦No worries Mike! Appreciate the response and keeping us all updated.
Is this still the case? I got the go example working but using the node example fails during dev with
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.Fails during dev as in local dev?
I see a max instances of 3 in that repos config. Could you be trying to spin up 4 instances?
Sory for late reply. I got it working by modifying the go worker using hono and a node server but couldn't for the life of me figure out why the provided node example wasn't working.... turns out it was this lol https://github.com/cloudflare/containers/blob/8265576291ae25107cb4967248b2bb74e02c5b5c/example-node/src/index.ts#L1