K
Q

Pushing the Docker image to Container Registry

7/8/2020

I am going through the Step 3: Push the Docker image to Container Registry on how to setup a docker image from Google Clound Engine to Kubernetes engine, from the following link though:

$ 

docker push gcr.io/${PROJECT_ID}/modo:v1
The push refers to repository [gcr.io/6267453573146657250/modo]
6a2e5ee87a10: Preparing
a276c90a34a4: Preparing
d675dcbcf549: Preparing
d675dcbcf549: Retrying in 1 second
0829f83db381: Retrying in 1 second
db7b61b8aab8: Retrying in 5 seconds
c5b2ac536264: Waiting
6c08a5b7d8f4: Waiting
c5b2ac536264: Waiting
6c08a5b7d8f4: Waiting
50867bb8f5d7: Waiting
72d6c6f0ea06: Waiting
8686c6b8d999: Waiting
44b57351135e: Waiting
00b029f9aa09: Waiting
18f9b4e2e1bc: Waiting
unknown: Project 'modo:6267453573146657250' not found or deleted.

I am sure the ID '6267453573146657250' is valid since it's the only project I have on the cloud engine.

-- staminna
docker
google-cloud-platform
google-kubernetes-engine
kubernetes

Similar Questions

How to schedule jobs in Kubeflow?
How to config my nginx.conf inside the openresty pod to route requests by query args to different k8s pods and keep the connections alive?
Connecting pod to external world
cpu and gpu resourcequota on kubernetes
Unable to connect GCP GKE cluster using client-go with GCP service account key

1 Answer

7/8/2020

You need to use the Project ID for PROJECT_ID, not the project number.

This guide explains where to find this info

enter image description here

Note that the Project ID in this example is my-sample-project-191923, not 314053285323. The latter is the project number.

-- jbielick
Source: StackOverflow