Dropping alpine linux/arm/v7

[bpatrik]

This is just for awareness and tracking conversation that I plan to drop linux/arm/v7 for alpine. It was done in: 3807a7b

Here is the error for why I did it: libvips/libvips#4618 (comment) (although I was too tired an opened it in the wrong repo :/)

Also linux/arm/v7 was last used in raspberry pi 2 so I was thinking that is old enough to drop support.

debian based distros still support v7.

I'm happy to readd v7 support for alpine if someone can make it work :)

[bpatrik]

Also dropped for debian

[grasdk]

Damn. Now I need an old edge-version before release of V3.

@bpatrik : would it be possible to go back in history to the latest commit where the build for ARM v7 worked and make a "final arm v7 release" something like v3.0.0−armv7−alpha. It would have many of the v3.0.0 features, hence the alpha-name?

All the old edge-versions have been overwritten on docker-hub, but this would make a permanent final arm v7 release, for the pi2 and pi3 owners. :)

[bpatrik]

Out of curiosity what on platform (hardware) are you using the arm v7?

If I remember correctly, sharp does not support v7 anymore, downgrading that would allow the app to build for v7. Or building Sharp from source is also an option. But doing so you might loose HEIC support.

I won't really have time for that, but happy to give some pointer on how to do so.

[grasdk]

I'm running it on a Raspberry Pi 3b for a small setup with less than 2000 pictures and videos.

I saw all the activity with sharp and compatibility... so I understand the decision to drop arm/v7. My wish was more in the lines of

• checkout the last commit ID that had a succesful build with arm v7
• call it V3.0.0-pre_alpha and build and release it on docker-hub with that name.

Reason: We had many nice edge-builds between v2.0.0 and v3.0.0 that also worked on arm v7, so it would be nice to have a final release that has as much as possible included. The pre_alpha name would indicate that it is unfinished, which is suitable if we go back to a commit in may or how far back we need to go.

So I guess what is needed is more like finding out which commit was the last to be able to build for arm v7 and then manually build and upload to docker hub. If you have an idea of the last time armv7 would build succesfully, then I can probably make a "recipe" to build the image.

[grasdk]

researching a bit more in the history, a candidate could be here:
https://github.com/bpatrik/pigallery2/tree/34cdd1380972b357eb74905ec656a7c39eba397b

This one was before all the library updates and just before the work on the extension functionality. It also looks like the build was successful, though all logs have expired:

https://github.com/bpatrik/pigallery2/actions/runs/16391029240#artifacts

[grasdk]

okay. I have an almost-recipe here-

command-recipe (assumes you have dockerx running)

$ git clone https://github.com/bpatrik/pigallery2.git pigallery2-300prealpha
$ cd pigallery2-300prealpha/
$ git fetch
$ git checkout -b version300prealpha 34cdd1380972b357eb74905ec656a7c39eba397b
$ git log -1 --pretty=format:"%H"
$ npm install
$ npm run create-release
$ mkdir pigallery2-release
$ cp pigallery2.zip pigallery2-release/
$ cd pigallery2-release/
$ unzip pigallery2.zip
$ rm pigallery2.zip
$ docker buildx build \
  --platform linux/arm/v7 \
  -t pigallery2:3.0.0-pre_alpha_alpine \
  -f ./docker/alpine/Dockerfile.build \
  . \
  --output=type=docker,dest=pigallery2-3.0.0-pre_alpha_alpine.tar

After this upload the tar-file to your pi and then load it (or use portainer as I did).

Then start a new container using this image.

There is a problem with videos, though. I need videos to work also. Should I make a sort of issue / sugestion for this? Any hints and help would be great. :)

[bpatrik]

that looks odd.

can you try the same on the release zip from here: https://github.com/bpatrik/pigallery2/releases/tag/3.0.1

although create release should do exactly the same

UPDATE: also you might need to revert sharp version back to a previous one.

[grasdk]

can you try the same on the release zip from here: https://github.com/bpatrik/pigallery2/releases/tag/3.0.1

Too new for arm/v7

UPDATE: also you might need to revert sharp version back to a previous one.

Yeah, I was not looking to reintroduce arm/v7 support, merely to be able to build some versions newer than 2.0.0 that has arm/v7 support.

I created a working solution here:

#1077

If you'd like it merged with your code, it should not interfere with anything. But it will allow you do release old versions, like the ones I'm after. I did a few here:
https://hub.docker.com/repository/docker/grasdk/pigallery2/tags

Would be cool if you'd add a couple of builds to your docker-hub. E.g. the 34cdd1380972b357eb74905ec656a7c39eba397b and e03cddb8533e87823a5be83fc214267d837406c7 commits.

[bpatrik]

Hi,
sorry lets take a step back. What would you like to achieve?

edge version (or in between releases) the app is only partially stable. I would rather not create a docker tag that points to a random version in the past as it might even have security vulnerabilities, but at lest known unfixed bugs.

Also if I create a git tag to any commit, it should the build workflow should create a release from it. (although that would probably fail on a past commit as it would use the latest workflow but old repo)

I see these as an option:

1. providing a simple tutorial for everyone to build the docker for themself. It should not be too hard.
   it would be something like:

   1. download the latest release zip and docker file from the repo
   2. run $ sudo docker build -t my-local-pigallery2 .
   3. use my-local-pigallery2 just like any other tag

2. You can try to resetup an older debian dockerfile that is still built for arm/v7 (see: https://hub.docker.com/_/node/tags?name=22-)

   • in the dockerfile, you would probably need to run something list RUN npm i sharp@OLDVERSION
   • I think this would allow to incluse the latest code with some older sharp and drop some photo types (like heic, arw)
   • this would involve a PR

3. you clone the repo figure out a version you would like to have and build it for you own and publish it under your user. (I don't mind adding to that repo a reference here in the app, so others would find it)

If you want to invest in it 2) would be reasonable. I'm 99% the only reason arm/v7 is not working is because of the latest sharp and vips. Downgrading sharp, should work again.