Why are there differnt tags for differnt architectures?

[Zoey2936]

I just wanted to ask why there are different tags for the different architectures, since docker image can have the same tag and can be used for multiple architectures?

[szaimen]

Hello, see #490

[Zoey2936]

So, do I understand correct, the problem is not pulling or running these images? It is that the update checking is not possible, since docker hub always report the checksum of the amd64 build, which would be always different from the checksum of the arm64 build and with that it will ever say that there is a new version? Or did is misunderstood the issue with one tag for both architectures?

[szaimen]

It is that the update checking is not possible, since docker hub always report the checksum of the amd64 build, which would be always different from the checksum of the arm64 build and with that it will ever say that there is a new version?

yes, this is the reason 👍

[Zoey2936]

I don't know if and how this would be possible and how makeable it is, but why not comparing the dates, the local images got created and the date the images on docker hub got created? The dates would always be the same.

[szaimen]

Honestly, changing this now will not allow us to get rid of the arm64 containers because many people already run it with these and it is not possible to change this for already existing instances, unfortunatley... I see the point of multiarch images but I don't think it is that bad to have different names for the different architectures...

[Zoey2936]

Images could still be pushed onto the arm tags, so that they exist, but are also multi arch, like the normal tags, this would not be a disadvantage in my opinion, if the check over the date would work. But I understand that multi arch images do not bring big advantages and this change would take some work, if it all even would work. It was just an Idea how this could be done.

[szaimen]

All right. Thanks for the brainstorming and bringing in some ideas on this! :)