Failure to provision Docker builder during deployment in self-managed cluster

Hey everyone,

I’m facing an issue with deploying a container in my self-managed Kubernetes cluster on Qovery. The deployment keeps failing during the Docker builder provisioning stage.

Here’s what’s happening:

  1. I trigger the deployment of my containerized application.
  2. Qovery successfully clones the repository, checks for an existing image in my Amazon ECR, and starts the image build process.
  3. The deployment gets stuck when trying to provision a Docker builder with 4000m CPU and 8GiB RAM.
  4. I see this error message repeatedly in the logs: “Cannot provision docker builder. Retrying…”.

I’ve tried a few things, but haven’t been able to resolve the issue. Has anyone else encountered this problem? Any suggestions on how to troubleshoot or fix this would be greatly appreciated!

Additional details:

  • Environment: Self-managed Kubernetes cluster on Qovery
  • Image repository: Amazon Elastic Container Registry (ECR)
  • Resource requirements for the Docker builder: 4000m CPU, 8GiB RAM

Thanks in advance for your help!

1 Like

Hi @Hussam1030 , I forwarded this to our team working on this part.

In the meantime, could you please explain how you installed Qovery on your Kubernetes cluster?

with qovery cluster install or qovery demo up command?