Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to deploy due to uncorrect Image Tag #8304

Closed
2 tasks done
imurata opened this issue Dec 20, 2024 · 1 comment
Closed
2 tasks done

Failed to deploy due to uncorrect Image Tag #8304

imurata opened this issue Dec 20, 2024 · 1 comment

Comments

@imurata
Copy link
Contributor

imurata commented Dec 20, 2024

Where is the problem?

https://docs.konghq.com/gateway-operator/1.4.x/get-started/kic/create-gateway/

What happened?

I copied and ran the GatewayConfiguration for On-Prem and got the following error.

  Warning  Failed     14s (x3 over 53s)  kubelet            Failed to pull image "kong:3.9.0": rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/library/kong:3.9.0": failed to resolve reference "docker.io/library/kong:3.9.0": docker.io/library/kong:3.9.0: not found

The following tag is incorrect.

          containers:
          - name: proxy
            image: kong:3.9.0

What did you expect to happen?

It should be stated as follows

          containers:
          - name: proxy
            image: kong/kong:3.9.0

Code of Conduct and Community Expectations

  • I agree to follow this project's Code of Conduct
  • I agree to abide by the Community Expectations
@mheap
Copy link
Member

mheap commented Jan 30, 2025

This isn't a typo. kong:3.9.0 is the official Dockerhub library version of Kong.

https://hub.docker.com/layers/library/kong/3.9.0/images/sha256-bb4f52545f6285352921f32f62062bea92e2c50172d165a50c353117e405af0c

@mheap mheap closed this as not planned Won't fix, can't repro, duplicate, stale Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants