@danielmayor, thanks for providing more context in our call.
To resolve this, we suggest setting up a delegated role permission from your primary ECR repository to the IAM Qovery user you’ve already configured. This approach leverages AWS’s cross-account role delegation capabilities, allowing the Qovery user to access your ECR repository with the necessary permissions.
By granting these permissions, Qovery can authenticate with your ECR registry effectively. This should resolve any issues related to the ‘FROM’ command in your Dockerfile, which points to an external ECR registry.
For a more detailed guide on how to set up these permissions, please refer to the following AWS documentation links:
- Creating IAM Roles - This page provides step-by-step instructions on how to create an IAM role in your AWS account.
- Tutorial: Using IAM Roles for Cross-Account Access - This tutorial walks you through the process of setting up cross-account access using IAM roles.
Let me know if that works for you 