Skip to content

Pod errors: ImagePullBackOff #483

Description

@lei-tang
  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.

  2. 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.

  3. 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".

Activity

  1. lei-tang commented on Sep 19, 2017

    @lei-tang
    ContributorAuthor

    #482 is the pull request corresponding to the fix for this issue.

  2. JustinBeckwith commented on May 4, 2018

    @JustinBeckwith
    Contributor

    👋 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!

  3. added a commit that references this issue on Nov 16, 2022
    e486d30
  4. added a commit that references this issue on Nov 16, 2022
  5. added 3 commits that reference this issue on Nov 17, 2022
    30a86a0
    b15fce1
    27d80dc
  6. added a commit that references this issue on Nov 17, 2022
    c54faf8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    🚨This issue needs some love.triage meI really want to be triaged.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions