-
Notifications
You must be signed in to change notification settings - Fork 5
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
Illegal instruction on armel #29
Comments
Hi @cspoonerprice, |
Hi @cspoonerprice, a new version of unbound is released. Let me know if it's fixed. |
Doesn't seem to be unfortunately. I cloned down the repo, and built the new image for linux/arm/v6:
Loaded, and tried to start the container. Here's the relevant logs:
|
Updated the unbound.sh file to list the opt/unbound/sbin dir and just run the unbound-anchor command without args:
Looks to me like building unbound in this way will successfully build, doesn't work on the linux/arm/v6 |
The issue is mentioned in NLnetLabs/unbound#1124 & waiting for unbound team response. |
as mentioned in the unbound ticket, the issue is with building the latest openssl version with unbound. Building openssl with OpenSSL_1_1_1-stable lets the build finish and run on v6 architecture. Unsure if this is a bug with unbound or working as intended with a need for a different build process on the pihole/unbound side. |
Let's wait for the unbound devs! |
@cspoonerprice any update on this? |
When using armel arch, on say a Rpi 1B+, the container will fail to start with:
/unbound.sh: line 420: 274 Illegal instruction (core dumped) /opt/unbound/sbin/unbound-anchor -a /opt/unbound/etc/unbound/var/root.key
Illegal instruction (core dumped)
This is a: Bug
Details with Docker log
s6-rc: info: service _startup successfully started
s6-rc: info: service pihole-FTL: starting
s6-rc: info: service pihole-FTL successfully started
s6-rc: info: service lighttpd: starting
s6-rc: info: service lighttpd successfully started
s6-rc: info: service _postFTL: starting
s6-rc: info: service _postFTL successfully started
s6-rc: info: service legacy-services: starting
Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
s6-rc: info: service legacy-services successfully started
/unbound.sh: line 420: 274 Illegal instruction (core dumped) /opt/unbound/sbin/unbound-anchor -a /opt/unbound/etc/unbound/var/root.key
Illegal instruction (core dumped)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service _postFTL: stopping
s6-rc: info: service _postFTL successfully stopped
s6-rc: info: service lighttpd: stopping
Stopping lighttpd
s6-rc: info: service lighttpd successfully stopped
s6-rc: info: service pihole-FTL: stopping
Stopping pihole-FTL
Terminated
How to reproduce the issue
Docker version 27.1.1, build 6312585
docker run command is default or you can specify the v6 platform:
docker run --platform=linux/arm/v6 -d --name pihole-unbound --name=pihole-unbound -e TZ=America/New_York -p 53:53/tcp -p 53:53/udp -p 80:80/tcp -e WEBPASSWORD='qwerty123' --restart=always rlabinc/pihole-unbound:latest
any additional info to help reproduce
Seems to reproduce on command pretty easily. Just have an rpi1 and try to run.
These common fixes didn't work for my issue
docker run
example(s) in the readme (removing any customizations I added)I've been able to get pihole/unbound working in combination using other community builds (chriscrowe), so it can work.
The text was updated successfully, but these errors were encountered: