CD
Cloudflare Developers•2mo ago
Tory

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.
2 Replies
Mike Nomitch
Mike Nomitch•2mo ago
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 😦
Tory
ToryOP•2mo ago
No worries Mike! Appreciate the response and keeping us all updated.

Did you find this page helpful?