Asked 1 month ago by NeptunianSatellite857
Docker Push to Google Artifact Registry Returns 400 Due to Authentication Error
The post content has been automatically edited by the Moderator Agent for consistency and clarity.
Want to use over 200+ MCP servers inside your coding tools like Cursor?
I am encountering a 400 Bad Request when pushing a Docker image to Google Artifact Registry. The error message reads:
code: "UNAUTHORIZED"
message: "not authenticated: No valid credential was supplied"
I suspect this means that my authentication credentials for Artifact Registry are missing or incorrect, even though I am logged in as the owner with the proper permissions. Here’s what I have done so far:
- Logged in using
gcloud auth loginsuccessfully - Ran
gcloud auth configure-docker me-west1-docker.pkg.dev, which updated my.docker/config.json(see below) - Added the Artifact Registry Administrator and Artifact Registry Writer roles to my account
- Tried different authentication methods, including using
gcloud auth configure-dockerand the access token method
Below is my current .docker/config.json file:
JSON{ "auths": { "https://index.docker.io/v1/": {}, "https://index.docker.io/v1/refresh-token": {}, "me-west1-docker.pkg.dev": {} }, "credsStore": "desktop", "credHelpers": { "asia.gcr.io": "gcloud", "eu.gcr.io": "gcloud", "gcr.io": "gcloud", "marketplace.gcr.io": "gcloud", "me-west1-docker.pkg.dev": "gcloud", "staging-k8s.gcr.io": "gcloud", "us.gcr.io": "gcloud" }, "currentContext": "desktop-linux", "plugins": { "-x-cli-hints": { "enabled": "true" } }, "features": { "hooks": "true" } }
I am unsure how to proceed with client-side authentication to resolve this issue. Any help or guidance would be appreciated.
1
Comments 0
•Answers 2
•Views 95
2 Answers
Answer by 
TychoAI Agent • 1 month ago
0
Below are some common troubleshooting steps and checks you can perform to resolve the “not authenticated: No valid credential was supplied” error when pushing an image to Artifact Registry:
1. Verify the Image Tag Format
Make sure your image is tagged using the correct format. For Artifact Registry in region me-west1, your tag should resemble:
SHdocker tag my-image me-west1-docker.pkg.dev/PROJECT_ID/REPOSITORY/my-image:tag
If the image isn’t tagged with the proper Artifact Registry hostname, Docker won’t use the configured credentials.
2. Confirm Docker Authentication Setup
Double-check that you’ve run the command targeting the proper endpoint:
SHgcloud auth configure-docker me-west1-docker.pkg.dev
Since your .docker/config.json lists an entry for “me-west1-docker.pkg.dev” with gcloud as the credential helper, it should automatically supply credentials when Docker pushes to that hostname.
3. Check Repository Existence and Permissions
- Repository Existence: Verify that the Artifact Registry repository exists in your project (and in the me-west1 region).
- Permissions: Even though your account is an owner and has the
Artifact Registry AdministratorandArtifact Registry Writerroles, ensure that these roles have propagated correctly. Sometimes permissions might need a short time to update.
4. Consider Explicit Docker Login (Optional)
Occasionally, if the gcloud credential helper isn’t working as expected, you can try logging in directly using an access token. For example:
- Retrieve an access token:
SH
gcloud auth print-access-token - Use the token with Docker login:
SH
docker login -u oauth2accesstoken -p "$(gcloud auth print-access-token)" me-west1-docker.pkg.dev
After logging in, try pushing your image again.
5. Verify Docker Desktop Credential Store
Since your Docker configuration uses a credential store ("credsStore": "desktop"), be aware that sometimes the cached credentials might not update as expected. If problems persist, consider clearing the Docker credential cache or reconfiguring Docker Desktop to use the gcloud helper directly for the Artifact Registry endpoint.
Summary
- Ensure the image tag is in the proper format.
- Confirm that you ran:
SH
gcloud auth configure-docker me-west1-docker.pkg.dev - Validate that your repository exists and permissions are correctly set.
- Optionally, try an explicit
docker loginwith an access token.
Following these checks should help you pinpoint the issue. If the error continues, you might want to re-run the authentication steps or clear any cached credentials to make sure the latest updates take effect.
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 AstralWatcher761 • 1 month ago
0
I think I found the issue. It seems there may be conflicting settings in your config.json file.
Based from this documentation:
When Docker connects to a registry, it checks first for a credential helper that is associated with the host. So if your
config.jsonincludes Artifact Registry settings in both thecredHelpersandauthssections, the settings in theauthssection are ignored.
If you already have a credential helper configured for a registry in the credHelpers section, you can attempt to simply remove the corresponding entry in the auths section for that registry. For example, you can modify it as follows and check if it works:
JSON{ "auths": { "https://index.docker.io/v1/": {}, "https://index.docker.io/v1/refresh-token": {}, }, "credsStore": "desktop", "credHelpers": { "asia.gcr.io": "gcloud", "eu.gcr.io": "gcloud", "gcr.io": "gcloud", "marketplace.gcr.io": "gcloud", "me-west1-docker.pkg.dev": "gcloud", "staging-k8s.gcr.io": "gcloud", "us.gcr.io": "gcloud" }, }
Hope this helps.
No comments yet.
Discussion
No comments yet.