Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Saiba mais sobre as etapas de solução de problemas que podem ser úteis se você tiver
problemas ao gerenciar imagens de contêiner no Artifact Registry.
Não é possível extrair uma imagem ou implantar em um Google Cloud ambiente de execução
Verifique se:
Verifique se o caminho completo da imagem que você está enviando está
correto. O caminho precisa incluir o nome do host do registro, Google Cloud,
ID do projeto, repositório e imagem. Exemplo:
Para as contas de serviço do Compute Engine, do Cloud Run e do Google Kubernetes Engine,
conceda o papel de leitor do Artifact Registry
(roles/artifactregistry.reader) à conta de serviço do ambiente de execução.
Para a conta de serviço do Cloud Build, conceda o papel de
Gravador do Artifact Registry (roles/artifactregistry.writer) à
conta de serviço que executa builds.
Se você estiver usando o Docker ou outra ferramenta de terceiros, faça o seguinte:
Não é possível enviar uma imagem para o Artifact Registry
Tente o seguinte:
Verifique se o repositório existe. Ao contrário do Container Registry,
o repositório de criação é uma operação separada do envio da primeira imagem. Se
ele não existir, crie um.
Verifique se o caminho completo da imagem que você está enviando está correto. O
caminho precisa incluir o nome do host do registro, o ID do projeto,
o repositório e a imagem. Google Cloud Exemplo:
Cada repositório do Artifact Registry é um recurso separado. Portanto, não é possível enviar
uma imagem para um caminho sem um repositório. Por exemplo,
us-west1-docker.pkg.dev/my-project/my-image:v1 é um
caminho de imagem inválido.
Para as contas de serviço do Compute Engine, Cloud Run e Google Kubernetes Engine,
conceda o papel de escritor do Artifact Registry
(roles/artifactregistry.writer) à conta de serviço do ambiente de execução.
Para a conta de serviço do Cloud Build, conceda o papel de
Gravador do Artifact Registry (roles/artifactregistry.writer)
à conta de serviço que executa builds.
Se o Artifact Registry retornar a mensagem The repository has
enabled tag immutability, a imutabilidade de tags será configurada para o
repositório. Não é possível enviar uma imagem com uma tag que já foi usada para
outra versão da mesma imagem no repositório. Tente enviar a imagem
novamente com uma tag que não seja usada por outras versões armazenadas da imagem.
Para verificar se um repositório está configurado para tags de imagem imutáveis, verifique
a coluna Tags de imagem imutáveis na lista de repositórios no
console Google Cloud ou execute o seguinte comando:
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-18 UTC."],[[["\u003cp\u003eThis page provides troubleshooting steps for managing container images in Artifact Registry, specifically addressing issues related to pulling and pushing images.\u003c/p\u003e\n"],["\u003cp\u003eWhen encountering problems pulling an image, ensure the image path is correct and that the pulling account has the necessary Artifact Registry Reader permissions.\u003c/p\u003e\n"],["\u003cp\u003eIf you are unable to push an image, confirm that the repository exists, the image path is correct, and the account has the appropriate Artifact Registry Writer permissions.\u003c/p\u003e\n"],["\u003cp\u003eTag immutability, when enabled, prevents pushing images with tags already in use by other versions of the same image, and checking the repository's configuration can help to fix this.\u003c/p\u003e\n"],["\u003cp\u003eIf you encounter \u003ccode\u003eImagePullBackOff\u003c/code\u003e or \u003ccode\u003eErrImagePull\u003c/code\u003e messages, you need to check the required permissions and then review the troubleshooting steps in the GKE documentation.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot container image issues\n\nLearn about troubleshooting steps that you might find helpful if you run into\nproblems managing container images in Artifact Registry.\n\n### Cannot pull an image or deploy to a Google Cloud runtime environment\n\nCheck the following:\n\n1. Verify that the full path of the image that you are pushing is correct. The path must include the registry hostname, Google Cloud, project ID, repository, and image. For example: \n\n us-west1-docker.pkg.dev/my-project/my-repo/my-image:v1\n\n For more information, see [Repository and image names](/artifact-registry/docs/docker/names).\n2. Verify that the account that is pulling the image has the correct [permissions](/artifact-registry/docs/access-control) to read from the repository. If you have [disabled automatic role granting to service accounts](/resource-manager/docs/organization-policy/restricting-service-accounts#disable_service_account_default_grants), then you must grant Artifact Registry roles to the runtime service accounts.\n - For Compute Engine, Cloud Run, and Google Kubernetes Engine service accounts, you must grant the Artifact Registry Reader role (`roles/artifactregistry.reader`) to the runtime service account.\n - For your Cloud Build service account, you must grant the Artifact Registry Writer role (`roles/artifactregistry.writer`) to the service account that runs builds.\n - If you are using Docker or another third-party tool, you must:\n - [Grant permissions](/artifact-registry/docs/access-control#grant) to the account that interacts with the repository.\n - Configure the client to authenticate to the repository.\n - [Docker authentication](/artifact-registry/docs/docker/authentication) instructions\n - [Troubleshooting containerd node images on Google Kubernetes Engine](/artifact-registry/docs/integrate-gke#troubleshooting_containerd_node_images)\n\n### Cannot push an image to Artifact Registry\n\nTry the following:\n\n1. Verify that the repository exists. Unlike Container Registry, repository creation is a separate operation from pushing the first image. If the repository does not exist, then [create](/artifact-registry/docs/repositories/create-repos) it.\n2. Verify that the full path of the image that you are pushing is correct. The path must include the registry hostname, Google Cloud project ID, repository, and image. For example: \n\n us-west1-docker.pkg.dev/my-project/my-repo/my-image:v1\n \n Each Artifact Registry repository is a separate resource, so you cannot push\n an image to a path without a repository. For example,\n `us-west1-docker.pkg.dev/my-project/my-image:v1` is an\n invalid image path.\n\n For more information, see\n [Repository and image names](/artifact-registry/docs/docker/names).\n3. Verify that the account that is pushing the image has [permissions](/artifact-registry/docs/access-control) to write to the repository. If you have [disabled automatic role granting to service accounts](/resource-manager/docs/organization-policy/restricting-service-accounts#disable_service_account_default_grants), then you must grant Artifact Registry roles to the runtime service accounts.\n - For Compute Engine, Cloud Run, and Google Kubernetes Engine service accounts, you must grant the Artifact Registry Writer role (`roles/artifactregistry.writer`) to the runtime service account.\n - For your Cloud Build service account, you must grant the Artifact Registry Writer role (`roles/artifactregistry.writer`) to the service account that runs builds.\n4. If Artifact Registry returned the message `The repository has\n enabled tag immutability`, then tag immutability is configured for the repository. You cannot push an image with a tag that is already used for another version of the same image in the repository. Try to push the image again with a tag that is not used by other stored versions of the image.\n\n To verify that the a repository is configured for immutable image tags, check\n the **Immutable image tags** column in the list of repositories in\n Google Cloud console or run the following command: \n\n ```\n gcloud artifacts repositories describe REPOSITORY \\\n --project=PROJECT-ID \\\n --location=LOCATION\n \n ```\n\n### ImagePullBackOff and ErrImagePull messages\n\nMessages with `ImagePullBackOff` and `ErrImagePull` indicate that an image\ncannot be pulled from the registry by GKE.\n\n- Verify the [requirements](/artifact-registry/docs/integrate-gke#permissions) to pull from Artifact Registry.\n- Review [Troubleshoot image pulls](/kubernetes-engine/docs/troubleshooting/image-pulls) in the GKE documentation."]]
