Pod errors: ImagePullBackOff #483
Comments
|
#482 is the pull request corresponding to the fix for this issue. |
|
👋 thanks for the issue! Based on the PR you provided, it looks like this has been fixed. If you're still running into issues... please do let us know! |
yoshi-automation
added
triage me
ace-n
pushed a commit
that referenced
this issue
Nov 16, 2022
telpirion
pushed a commit
that referenced
this issue
Nov 16, 2022
ace-n
pushed a commit
that referenced
this issue
Nov 17, 2022
ace-n
pushed a commit
that referenced
this issue
Nov 17, 2022
* updated CHANGELOG.md [ci skip] * updated package.json [ci skip] * updated samples/package.json Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
ace-n
pushed a commit
that referenced
this issue
Nov 17, 2022
* updated CHANGELOG.md [ci skip] * updated package.json [ci skip] * updated samples/package.json Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
ahrarmonsur
pushed a commit
that referenced
this issue
Nov 17, 2022
ace-n
pushed a commit
that referenced
this issue
Nov 17, 2022
* updated CHANGELOG.md [ci skip] * updated package.json [ci skip] * updated samples/package.json Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
ace-n
pushed a commit
that referenced
this issue
Nov 17, 2022
* updated CHANGELOG.md [ci skip] * updated package.json [ci skip] * updated samples/package.json Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
ace-n
pushed a commit
that referenced
this issue
Nov 17, 2022
* updated CHANGELOG.md [ci skip] * updated package.json [ci skip] * updated samples/package.json Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Shabirmean
pushed a commit
that referenced
this issue
Feb 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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".
The text was updated successfully, but these errors were encountered: