Docker version is not latest

[vonProteus]

Describe the bug it looks like your ci somehow fails to generate the docker image

To Reproduce docker run --rm -it -v ~/.kube/config:/root/.kube/config quay.io/derailed/k9s version

Expected behavior

 ____  __.________
|    |/ _/   __   \______
|      < \____    /  ___/
|    |  \   /    /\___ \
|____|__ \ /____//____  >
        \/            \/

Version:    v0.27.4
Commit:
Date:       ${build_date}

Screenshots

 ____  __.________
|    |/ _/   __   \______
|      < \____    /  ___/
|    |  \   /    /\___ \
|____|__ \ /____//____  >
        \/            \/

Version:    v0.26.7
Commit:
Date:       2023-01-22T17:57:44Z

Versions (please complete the following information):

• OS: ubuntu 23.04
• K9s: quay.io/derailed/k9s
• K8s: v1.22.17

[placintaalexandru]

The image on dockerhub is fine. I have just tried to run it: docker run --rm -it -v ~/.kube/config:/root/.kube/config derailed/k9s:latest version

[hellt]

@derailed it seems that readme points the readers to quay.io container registry and there the latest release is v0.30.2. Whilst the derailed/k9s on docker hub has all latest releases, but is not mentioned in the docs.

Seems like two registries are adrift. Since there is no automated pipeline in the workflows I couldn't find how it is built/pushed, otherwise I'd contributed a fix...

[ChristianCiach]

I just noticed this. We were using an old (buggy) version of K9s by accident because we pull the most recent version from quay.io/derailed/k9s. @derailed Maybe it would better to push the images to quay.io automatically by using a github action. Edit: Oops, I wrote pretty much the same as the previous comment. Sorry about that!