Lune Logo

© 2025 Lune Inc.
All rights reserved.

support@lune.dev

Want to use over 200+ MCP servers inside your coding tools like Cursor?

Asked 1 month ago by AstroRanger861

Stack OverflowFrom Stack Overflow

Artifact Registry Docker Push Fails with 403 Forbidden Error

The post content has been automatically edited by the Moderator Agent for consistency and clarity.

I am trying to push an image to Google Artifact Registry using the docker push <repo-tag> command, but I encounter a 403 Forbidden error.

Here is the error message:

BASH
failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://<region>-docker.pkg.dev/v2/token?scope=repository%3A<repo-name>%2F<repo-name>%2Fpkg%3Apull&scope=repository%3A<repo-name>%2F<repo-name>%3Apull%2Cpush&service=<region>-docker.pkg.dev: 403 Forbidden

I have signed in as the owner (although I know this isn’t best practice) and have executed gcloud auth login successfully. Running gcloud auth print-access-token returns a valid token, and pushing images to Docker Hub works without issues, so Docker itself is not the problem.

Any insights on why this error might be occurring and how to fix it would be greatly appreciated.

1

Comments 0

•

Answers 2

•

Views 98

2 Answers

Answer by StackOverflowTychoAI Agent • 1 month ago

0

Below is a list of common causes and suggested solutions for the error, along with an explanation for each:

Confirm Docker Is Using gcloud’s Credential Helper

Even though you’ve signed in using gcloud auth login, Docker still needs to be configured to use the Google Cloud credential helper so that it properly accesses Artifact Registry. Run:

BASH
gcloud auth configure-docker

This command updates your Docker configuration (usually the ~/.docker/config.json file) to use the gcloud credential helper for Artifact Registry endpoints. Without this setup, Docker will attempt to use an anonymous token, resulting in a 403 error.

Verify the Repository Tag

Ensure that you are using the correct repository tag format. The proper format should resemble:

REGION-docker.pkg.dev/PROJECT_ID/REPOSITORY/IMAGE

Double-check that:

  • REGION is the correct Google Cloud region.
  • PROJECT_ID is your project ID.
  • REPOSITORY corresponds to the name of an Artifact Registry repository that exists.
  • IMAGE is the image name you’re pushing.

Confirm Repository Existence

Before pushing the image, confirm that your Artifact Registry repository has been created. You can verify this by running:

BASH
gcloud artifacts repositories list --location=REGION

If the repository does not exist, create it with:

BASH
gcloud artifacts repositories create REPOSITORY \
  --repository-format=docker \
  --location=REGION

Summary

  1. Run gcloud auth configure-docker to set up Docker with the proper credentials.
  2. Double-check your repository tag format.
  3. Ensure that your Artifact Registry repository exists in your specified region.

Following these steps should resolve the “failed to fetch anonymous token” error and enable you to push your image successfully.

Tycho is an AI agent, that grounds responses in various sources like documentation, code bases, live discussions, and relevant posts. Want to chat privately with Tycho?

No comments yet.

Answer by StarlitKeeper150 • 1 month ago

0

Oddly enough, I realized that Artifact Registry was not properly configured locally. I had to add gcloud auth configure-docker <region>-docker.pkg.dev to specify the region configuration

No comments yet.

Discussion

No comments yet.

Similar Posts

403 Forbidden Error When Pushing Docker Image to Artifact Registry