v1.2.4 does not work with Synology NAS

[update-freak]

Hi,
I'm currently haveing the issue test after updating to v1.2.4 the container does not work on my Synology NAS with the System DSM 7.2.2 (latest OS).
v1.2.3 works without problem.

Maybe linked to the old kernel:
uname -r
3.10.108

Let me know if I can help in providing logs or test something

[johnwarne]

Does the container successfully start up? If not, what errors are shown?

[update-freak]

In portainer the logs does not show any error, only the arrow-logo was included multiple times (but I changed the docker compose to restart: always).I tried it also with v1.2.5. Access via the URL don't work

[update-freak]

Maybe the reason is the processor of my Synology 716+ (ARMv7 32-bit) and that its now only working with amd64 (x86_64) or arm64?

[johnwarne]

Hmm… maybe? The platforms specified in the release.yml haven't changed since the initial 1.0 was pushed (linux/amd64,linux/arm64). Is there anything else that has changed in your setup between the time 1.2.3 was released (March 6th) and now? Perhaps it's also possible to specify an ARMv7 32-bit image in the release.

[update-freak]

checked it again. With v1.5.1 (latest; see docker compose below) it's not working, but with v1.2.3 it's working.

services:
  upvote-rss:
    image: ghcr.io/johnwarne/upvote-rss:latest
    platform: linux/amd64
    container_name: upvote-rss
    environment:
      - REDDIT_USER=beispiel
      - REDDIT_CLIENT_ID=beispiel
      - REDDIT_CLIENT_SECRET=beispiel
      - TZ=Europe/Berlin
    volumes:
      - /volume1/docker/upvoterss:/app/cache
    ports:
      - "1071:80"
    restart: always

Nothing else changed on my setup. I also tried it with a fresh installed NAS docker and got the same result

[johnwarne]

Will it work if you remove the line specifying platform: linux/amd64?

[update-freak]

no, unfortunatelly not. Still same problem

[update-freak]

I also tried the v1.6.0. Same results -> restarts

[update-freak]

@johnwarne Could it be to updated dependancys? Any idea how to continue with this problem? I'm also available to help testing

[johnwarne]

@update-freak I've just released v1.8.0 which should add support for 32-bit ARMv7. Can you try pulling the new image and seeing if the container will run on your Synology? I tested on a 32-bit Raspberry Pi 3B and it seems to be running as expected.

[update-freak]

Thanks.
I tried with latest-tag, but got same result.
Synology DS716+ is using a 64 bit architecture.

But with ChatGPT I got the replay that
the change from frankenphp:1.4.4-php8.4.4-alpine to
frankenphp:1.9.0-php8.4.10-alpine in Version 1.2.3 to 1.2.4 could be a possible root cause that I end up in boot loops (because the kernel of my Synology DS716+ is quite old).

Would it be possible if you could provide a "legacy" version with frankenphp:1.4.4-php8.4.4-alpine?

[update-freak]

@johnwarne Can you provide a version with frankenphp:1.4.4-php8.4.4-alpine or how I can test this?

EDIT: Tried again with the latest-tag and without always-restarts. I recognised that I received the "exited - code 139" (maybe that helps)

[update-freak]

@johnwarne Let me know if can test something? Still have this problem with the latest version