Hey Sudarshan, thanks for your question!

That error is saying that the current servers you have deployed do not currently have enough unallocated resources to fulfill the action you're trying to accomplish. You can get a quick view of the currently allocated resources on the clusters page under infrastructure.

I've included a link to Container Resources in our docs to help explain what this is.

Please let me know if you'd like me to add more context, and I'd be happy to dive in further.

Hey all, we were also having this "issue" and are a bit confused as to how the resource allocation works.

The resource allocation seems to count all containers that are stopped. We were only able to free up CPU shares by deleting containers. Is this intended?

The docs state that environment level containers like load balancers do not count towards the usage of clusters. Yet, Cycle seemed to have automatically stopped the load balancer of one of our environments, when we tried to deploy a new container while hitting our maximum CPU allocation. Attempting to restart the load balancer resulted in the same error message as described by Sudarshan. (container name is "Environment Load Balancer" in the message) Is this intended?