guestbook-go/guestbook-controller.yaml imagepullbackoff

[craigboman]

The image: registry.k8s.io/guestbook:v3 is causing an imagePullBackOff error. I don't think this image is still available. Can't find it anywhere. Currently guestbook-controller.yaml is broken until we can resolve the imagepullbackoff error by fixing the image. Doesn't seem to be an issue with any other images, just this one. However, I haven't tried applying any of the subsequent yaml in the example setup readme for the guestbook-go cluster.

[AmarNathChary]

If you have access to the pod’s events or logs could you share the detailed error message associated with the ImagePullBackOff

[parth-srivastav]

I ran a describe on the pods - this is the full error that I saw

Failed to pull image "registry.k8s.io/guestbook:v3": failed to pull and unpack image "registry.k8s.io/guestbook:v3": failed to get converter for "registry.k8s.io/guestbook:v3": Pulling Schema 1 images have been deprecated and disabled by default since containerd v2.0. As a workaround you may set an environment variable CONTAINERD_ENABLE_DEPRECATED_PULL_SCHEMA_1_IMAGE=1, but this will be completely removed in containerd v2.1.

[rvs1729]

https://github.com/kubernetes/examples/pull/544

[jayeshmahajan]

This is completed can be closed?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[jayeshmahajan]

/close

[k8s-ci-robot]

@jayeshmahajan: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.