Closed ikawaha closed 1 year ago
I'm not sure yet but it seems that "something happened" to the pushed image in DockerHub side during release flow.
Because the local build before push to DockerHub seems success. But failed on pulling back the pushed image.
Can you re-run the failed job in the "release" workflow? If not, we should add a "workflow_dispatch:" in the workflow YAML.
Though, I have a feeling that qemu
or buildx
had made a change for the cause. I will report as soon as I found something.
Thanks for your comment.
I retried the failed workflow with the same result. I also tried adding workflow_dispatch
and running it manually, which also failed. ๐ค
Hmmm ... ๐ค
I wonder why is the latest
image tag not updated since 3 months. Maybe the manifest error is related to this.
I finally found out the reason.
We were using an old method to tweak around to support Docker images for 32 bit ARM architectures. Such as ARM v6l
and v7l
. The old Docker did support ARM v6
but not ARM v6l
, such as RaspberryPi Zero, so we needed a tweak.
But now we do not need any tweak and can be done via goreleaser
.
Before PR, I made an example repo as a proof of concept.
@KEINOS Thank you for your research! I will try to set it up.
@ikawaha If you haven't taken care of it yet, I'd like to send you a PR if you don't mind.
I opened a draft PR @ https://github.com/ikawaha/kagome/pull/301
I haven't pushed much yet. But if you have already done something plz feel free to point that out!
@KEINOS Thank you so much! I haven't been able to start yet, so thank you in advance.
I confirm that the latest image (ikawaha/kagome:latest
) worked in all the below 3 architectures. :tada:
https://github.com/ikawaha/kagome/actions/runs/4335647896/jobs/7570442414
Pull back the image failed: