linuxserver / docker-jackett

GNU General Public License v3.0
390 stars 96 forks source link

[BUG] Can't run v20 in armv7 32b #140

Closed vromero closed 1 year ago

vromero commented 1 year ago

Is there an existing issue for this?

Current Behavior

When running in a Western Digital My Cloud EX4100 I get segmentation fault for the multiple v20 that I have tried.

root@WDMyCloudEX4100 HD_a2 # docker run --platform linux/arm/v7  -it --rm linuxserver/jackett:v0.20.1066-ls66
Unable to find image 'linuxserver/jackett:v0.20.1066-ls66' locally
v0.20.1066-ls66: Pulling from linuxserver/jackett
f818528f8d77: Pull complete
cb9ed8652433: Pull complete
0f6c01b062d0: Pull complete
397aa4dc7936: Pull complete
480d7ca3241d: Pull complete
ae956e62f412: Pull complete
204de8489f14: Pull complete
83335e6f42a7: Pull complete
376a67e0a322: Pull complete
Digest: sha256:e65c648f0705c8e23723bfa35dce79d13f7382cf183dd0591084c7bb4722202a
Status: Downloaded newer image for linuxserver/jackett:v0.20.1066-ls66
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 01-migrations: executing...
[migrations] started
[migrations] no migrations found
[cont-init.d] 01-migrations: exited 0.
[cont-init.d] 02-tamper-check: executing...
[cont-init.d] 02-tamper-check: exited 0.
[cont-init.d] 10-adduser: executing...
usermod: no changes

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/

Brought to you by linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    911
User gid:    911
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-scripts: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault

When I try v19 it seems to work:

root@WDMyCloudEX4100 HD_a2 # docker run --platform linux/arm/v7  -it --rm linuxserver/jackett:development-v0.19.275-ls282
gle commit messageUnable to find image 'linuxserver/jackett:development-v0.19.275-ls282' locally
development-v0.19.275-ls282: Pulling from linuxserver/jackett
c9e9be333ef6: Pull complete
68e269c1e278: Pull complete
57c3344ee94c: Pull complete
1b9be4d5cef7: Pull complete
7f7c8a431ae6: Pull complete
d8110592b06f: Pull complete
70d730f75bdb: Pull complete
62960e1eefc7: Pull complete
83f3a05a839b: Pull complete
Digest: sha256:fc746cea7dd2e98fcdb2639f4e85f79f3b62047153563f48ab1bd3ee66990106
Status: Downloaded newer image for linuxserver/jackett:development-v0.19.275-ls282
Toggle commit message[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 10-adduser: executing...
usermod: no changes

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/

Brought to you by linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    911
User gid:    911
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-scripts: executing...
[custom-init] no custom files found exiting...

Expected Behavior

It should work in this supported platform

Steps To Reproduce

docker run --platform linux/arm/v7 -it --rm linuxserver/jackett:v0.20.1066-ls66

Environment

- OS:
- How docker service was installed:

CPU architecture

armhf

Docker creation

docker run --platform linux/arm/v7  -it --rm linuxserver/jackett:v0.20.1066-ls66

Container logs

see above
github-actions[bot] commented 1 year ago

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

thespad commented 1 year ago

I've tested the latest 32-bit Arm build locally and it runs just fine, I've also tested the build you're using, which is nearly a year old, and that works fine too.

That said, I don't have a Western Digital My Cloud to test with, and I have no idea how ancient their Docker version might be.

Additionally, please see our recent statement on 32-bit Arm support: https://www.linuxserver.io/armhf

vromero commented 1 year ago

Fair enough, thanks for taking the time to take a look and reply, very much appreciated.

svonidze commented 10 months ago

for those who are concerned of why there is no more armv7 version in hub.docker.com

As we previously announced, due to the ever-decreasing support for modern apps and packages on 32-bit Arm platforms, we have now deprecated all 32-bit Arm (armhf) versions of our images effective today, 2023-07-01. ... https://info.linuxserver.io/issues/2023-07-01-armhf/