Learn how to resolve the GCP Docker Push Access Denied error. Our Google Cloud Support team is here to help you with your questions and concerns.

GCP Docker Push Access Denied | 3 Solutions

If you are having trouble with the “permission denied” error when trying to push a Docker container to the Google Container Registry, you have come to the right place.

Solution 1: Adjust VM Instance Access Rights

A common cause for the permission denied error is insufficient access rights on the VM instance. Here’s how to fix it:

To begin with, grant access rights when creating the VM instance. This is done during the instance creation process or by editing the instance settings later on. There are two ways to manage access:

• Option 1: Select “Allow full access to all Cloud APIs” under Identity and API access.
• Option 2: Choose “Set access for each API” and then set “Read Write” access for Storage.

Solution 2: Verify Bucket Permissions with gsutil

Sometimes, we must double-check our permissions directly on the Google Cloud Storage bucket. Here’s how:

1. We can use gsutil to examine the Access Control List (ACL) for the bucket:

   $ gsutil acl get gs://
2. Then, make sure the account has the necessary permissions.

Solution 3: Fine-tune Docker Push Commands

If the permission issue persists, it is probably because the account does not have permission to store/write the docker image in GCR.

As a Google cloud storage bucket backs the GCR, our account needs write permission on the bucket.

For eu.gcr.io, the corresponding bucket is gs://eu.artifacts.$PROJECT_ID.appspot.com.

In the comments, let us know which of the above solutions helped you.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to resolve the GCP Docker Push Access Denied error.