Closed NickBusey closed 4 years ago
Yeah, we're aware, and have been for some time, but it requires time which, I specifically, do not have. It's definitely something we want to do, but we have no ETA at this time.
Ok, I would be willing to help on this if it's desired.
Thanks, we appreciate it. One of the other members, I believe, has experience with the manifests so I've started a conversation with him and CauseFX about this.
Chris
On Tuesday, April 7, 2020, 11:17:25 AM EDT, Nick Busey <notifications@github.com> wrote:
Ok, I would be willing to help on this if it's desired.
— You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.
This has been on the timeline for a while, and two of the three criterias has been filled for a few months, the last piece of the puzzle is php7.4 hitting the alpine package repo.
Currently Organizr tags it's separate architecture images differently.
The
latest
tag is onlyamd64
, to use this image on ARM, you have to point it to an architecture specific tag likearm64
orarmhf
.This complicates deployment and causes unnecessary user friction.
Nextcloud for example, does this correctly. Their
latest
tag supports a whole slew of architectures.Take a look at https://hub.docker.com/_/nextcloud/?tab=tags vs https://hub.docker.com/r/organizrtools/organizr-v2/tags to see what I mean.
If Organizr could use docker manifests the way Nextcloud does, I wouldn't have to do things like this in my ansible code: