-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add support for 32k page size (ARM?) to avoid ELF load command address/offset not page-aligned
#2078
Comments
This will likely need to be fixed upstream (either the official community PHP Docker image or the Debian one), but I'm honestly not sure. Someone needs to do the leg work to research this matter more, including not only a possible fix for this situation, but a path that makes sure it doesn't break things for others. I think it's ARM specific. |
ELF load command address/offset not page-aligned
I was looking to see how other Official Docker Library images have dealt with this and I found:
Though from general searches (i.e. outside Docker Library images) I'm surprised this hasn't come up a bit more often with the Official ones. 🤔 |
Some related posts... |
Also i try experiment in emulation on x86 like this.
Alpine Linux 3.17.0 under emulation page size 32k give me And backward on QNAP with pagesize 32K container
|
Hello,
recently QNAP container station switched to 32k page size from 4k and since then I am having problem with update (last working image, that I had tried is NextCloud 26.0.1, tried to update to 26.0.7 and since then I am having problem starting the container up (no matter if its apache, fpm, etc.). I am getting messages like:
And the container is still restarting. I had searched the internet and it seems that its related to change to 32k page size. I am not sure if i am able to change it back to 4k though (official QNAP support help is... I don't want to be rude).
Is it possible to make images compatible to 32k, maybee backwards compatible, since I want to upgrade from 26.0.1 to latest release (which is I gues to 26.0.7 and then do 27.0.0 and then to latest).
Thanks,
Regards,
Petr Sourek
The text was updated successfully, but these errors were encountered: