-
-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nzbget segfaults with time64 on arm32 #127
Comments
I already submitted a bug report with nzbget, but I don't expect immediate resolution, and the arm32 builds won't work, in the meantime. The issue is that with v21.0-ls71, Alpine was was upgraded to 3.13, which uses musl 1.2.2. As of 1.2.0, musl uses time64, even on 32-bit archs:
I asked about legacy compatibility on the musl IRC and was told that apps built against the old headers will continue to use time32. I tested this by compiling nzbget on Alpine 3.12 in the build stage then running it on Alpine 3.13, and it works fine. I also tested it on the latest Ubuntu base image (which obviously doesn't use musl), and it worked fine (with nearly double the image size). I'm happy to submit a PR for either of those scenarios. For anyone that ends up here that wants a quick fix, just roll back to linuxserver/nzbget:v21.0-ls70 for now. |
Sounds like you need to upgrade your libseccomp2: https://docs.linuxserver.io/faq#my-host-is-incompatible-with-images-based-on-ubuntu-focal |
Also, if the nzbget binary is compiled on Alpine 3.12, it runs on Alpine 3.13 without issue. |
I think compiling on 3.12 until/if this get fixed upstream is the best approach. |
[armhf] revert linuxserver#125 and use py3-cryptography alpine package, avoiding rust-lang/cargo#9187 closes linuxserver#127
Expected Behavior
nzbget should not segfault on arm32
Current Behavior
nzbget segfaults when a time is encountered (when an nzb is in the queue or history).
Steps to Reproduce
Environment
OS: linux
CPU architecture: arm32
How docker service was installed: from the official docker repo
Command used to create docker container (run/create/compose/screenshot)
Docker logs
The text was updated successfully, but these errors were encountered: