Skip to content
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

nginx:1.26.0 does not run on RPi 5. ELF load command address/offset not page-aligned #884

Closed
sholdee opened this issue Apr 24, 2024 · 3 comments

Comments

@sholdee
Copy link

sholdee commented Apr 24, 2024

Describe the bug

Nginx docker image no longer works on RPi5 after the 1.26.0 update. Tag 1.25.5 was working without any issues.

The container crashes immediately and logs error:

/bin/sh: error while loading shared libraries: libc.so.6: ELF load command address/offset not page-aligned

To reproduce

Steps to reproduce the behavior:

  1. Deploy nginx:1.26.0 on RPi 5 running Pi OS Bookworm 64-bit
  2. View container logs
  3. Observe error

Expected behavior

The container launches.

Your environment

  • K3s 1.28.8
  • nginx:1.26.0
  • Kubernetes
  • RPi 5
  • Pi OS Lite 64-bit (Debian Bookworm)

Additional context

The container worked fine in this environment until the 1.26.0 update. Nothing else was changed except updating the image tag on my deployment from 1.25.5 to 1.26.0.

It appears to be due to 16k page size on this platform: raspberrypi/bookworm-feedback#107

Evidently something in the 1.26.0 update broke compatibility.

@thresheek
Copy link
Collaborator

That's interesting - 1.25.5 and 1.26.0 are identical code!

@thresheek
Copy link
Collaborator

Can you show your nginx full configuration?

@sholdee
Copy link
Author

sholdee commented Apr 24, 2024

Can you show your nginx full configuration?

Sure, here is one of the configs: https://github.com/sholdee/k3s-app-manifests/blob/master/hass/zwaveui-proxy/zwaveui-proxy-secret.yml

This puzzled me too, so I went ahead and purged all cached images on my nodes:

sudo k3s crictl rmi --prune

Re-pulling the image seems to have resolved the issue and my containers are running 1.26.0 now. Strange issue, but looks to have been on my end. Thank you!

@sholdee sholdee closed this as completed Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants