Closed bgoareguer closed 1 year ago
Hey @bgoareguer! Thanks for reaching out, yes something definitely went wrong with the Docker builds in the last release (due to breaking changes in goreleaser).
I've published an experimental multi-arch (arm64 and amd64) container as zegl/kube-score:v1.16.0-dev
. It contains kube-score, helm3, and kustomize. Could you please give it a test, and let me know if it works for you?
The zegl/kube-score:v1.16.0-dev
image works great for x86_64:
I cannot test it on arm64 since I do not have such hardware to test on but I can see the arm64 image on Docker Hub.
The only issue I saw is that the kube-score binary has been added twice in the image:
$ find ./ -name kube-score
./kube-score
./usr/bin/kube-score
Great, thanks for your help!
Yes, the binary was added twice for backwards compatibility with the previous generation of images. Some had the kube-score binary at /kube-score
and some in /usr/bin/kube-score
. Thinking of it tough, one of those could be a symlink...
I'll add the symlink and make a new release of kube-score. :-)
Hi @zegl! One last thing: it seems you already had a zegl/kube-score:latest image on quay.io but this image is not up to date. Can you please either delete this image from quay.io or update it?
I am using a Docker mirror that searches for images in quay.io before docker.io, so it always returns me the old image from quay.io.
@bgoareguer Oh, I'd totally forgotten about quay. I'll see what I can do, it seems like Red Hat has blocked my account (logging in sends me to this article). I'll see what I can do to recover it.
Which version of kube-score are you using?
I am using the
zegl/kube-score:v1.15.0-helm3
docker image on an x86_64 system:What did you do?
I pulled the Docker image from the Docker Hub with the following command:
I then tried to run kube-score with the following command:
What did you expect to see? I expected kube-score to run without warning
What did you see instead?
Docker shows a warning telling me that the image I am trying to run does not match my host platform:
Additional details
The digest of the image I pulled:
Even though I pulled the image from a x86_64 system, I got an arm64 image:
On Docker Hub, the
zegl/kube-score@sha256:8e794bb74eb171d065f4faed7d43f3a08995e2ce106326368eaf280a3701383b
docker image corresponds to a arm64 image. It seems no image has been published for the x86_64 architecture.Kube-score manages to scan my manifest because the kube-score binary is a x86_64 binary. After extracting the image, here is the result of the file command on the kube-score binary that was inside the image:
So a x86_64 binary has been copied into an arm64 Docker image and no x86_64 image has been published.
Can you please: