gaut
gaut

Reputation: 5958

docker push to google cloud GCP fails with name unknown: Buckets

Trying to push a local image to a google cloud project, which fails with this error. Any help?

$ docker push gcr.io/myprojectID/myrstudio:latest
The push refers to repository [gcr.io/ myprojectID  /myrstudio]
07fc541c7837: Preparing
5f40edd3a036: Preparing
8243f7003c86: Preparing
55903d33bbd7: Preparing
6f15325cc380: Preparing
1e77dd81f9fa: Preparing
030309cad0ba: Preparing
1e77dd81f9fa: Waiting
030309cad0ba: Waiting
6f15325cc380: Layer already exists
1e77dd81f9fa: Layer already exists
030309cad0ba: Layer already exists
55903d33bbd7: Pushed
07fc541c7837: Pushed
5f40edd3a036: Pushed
8243f7003c86: Pushed
name unknown: Buckets(myprojectID  ,artifacts. myprojectID.appspot.com)

Looks like something was pushed, but at some point failing...

EDIT: running wind 10 version 20H2 (OS build 19042.1288)

Upvotes: 4

Views: 2472

Answers (1)

Wojtek_B
Wojtek_B

Reputation: 4443

When you perform a docker push to Google Container Registry your image is stored inside a bucket in your project;

Container Registry uses Cloud Storage buckets as the underlying storage for container images. You control access to your images by granting permissions to the bucket for a registry.

If this is a first time that you try to push an image - the account you're using must have Storage Admin role. That's because a bucket that will store your images has to be created.

Have a look at the documentation that describes all the steps to grant necessary permissions.

If you're not familiar with GCP Cloud Storage then have a look at the guide describing how to use GCP's storage buckets.

Also you may consider trying out Artifact Registry which gives you more control over your images.

Upvotes: 1

Related Questions