-
Notifications
You must be signed in to change notification settings - Fork 19
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
fr24feed operation not permitted #241
Comments
I had exactly the same problem with the arm64 builds on a Raspberry Pi 5. Had to rollback to 1.0.44 for a working version. |
Just found a workaround for this - add the NET_RAW capability to your container. I'm not sure what's changed to require this. I'm running via rootless Podman 4.9.4 on Debian cc @jbrazio |
Brilliant, got it running now as well. Debian Bookwork using podman on a Pi 5 |
I am also receiving a similar error:
If I change my the release tag from Unfortunately the implementation of docker I'm using doesn't support adding arbitrary capabilities at the moment, so rolling back updates is the only solution at the moment. Anything newer, such as any variation of |
Note that we are removing As for environment:
- WATCH_INTERVAL=infinity I'll add some wording to the README to describe this work-around thanks - kx1t |
One more thing -- I can't test this because I don't have a Pi5 to my disposal, but some arm64 binaries don't run natively on Pi5, because in many of the Pi5 Linux Kernel images, the Kernel Page Size is set to 16K. Several apps are only compatible with 4K Kernel Page Sizes. This could possibly be the cause of See here for a work-around (which is basically setting your Kernel Page Size to 4K on the Pi5) |
Seems to be an issue in 1.0.46-2_linux_amd64_nohealthcheck, not present in 1.0.46-2_linux_amd64_nohealthcheck where /usr/local/bin/fr24feed cannot be executed.
This originally manifested as repeating error in stdout:
On further investigation, this was nothing to do with arm or invalid ELF images, but because the s6 scripts/fr24feed naively assumes that if
/usr/local/bin/fr24feed --version
doesn't run, it should try again withqemu-arm-static
. Since the binary cannot be exec'd, the--version
test fails, and the script incorrectly tries to launch an amd64 ELF binary withqemu-arm-static
wrapper.The simplest reproduction case demonstrating the issue:
Broken in
1.0.46-2_linux_amd64_nohealthcheck
Working in
1.0.46-1_linux_amd64_nohealthcheck
:Injecting strace into the latest image doesn't yield any interesting reason as to why the binary cannot be
execve
'd:This is running on a host with selinux disabled, so is not an avc denial.
The text was updated successfully, but these errors were encountered: