You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The cause of the problem
This problem is caused by the following line in nodejs-docs-samples/endpoints/getting-started/container-engine.yaml:
image: b.gcr.io/endpoints/endpoints-runtime:0.3
The container registry b.gcr.io has been deprecated, thereby causing the problem of running the image.
Fix for the problem
Change the following line in nodejs-docs-samples/endpoints/getting-started/container-engine.yaml from "image: b.gcr.io/endpoints/endpoints-runtime:0.3" to "image: gcr.io/endpoints-release/endpoints-runtime:1".
Description of the issue:
When running the example in https://cloud.google.com/endpoints/docs/get-started-container-engine#node, the container engine cluster for esp encounters pod errors: ImagePullBackOff.
The cause of the problem
This problem is caused by the following line in nodejs-docs-samples/endpoints/getting-started/container-engine.yaml:
image: b.gcr.io/endpoints/endpoints-runtime:0.3
The container registry b.gcr.io has been deprecated, thereby causing the problem of running the image.
Fix for the problem
Change the following line in nodejs-docs-samples/endpoints/getting-started/container-engine.yaml from "image: b.gcr.io/endpoints/endpoints-runtime:0.3" to "image: gcr.io/endpoints-release/endpoints-runtime:1".