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

The futex facility returned an unexpected error code on Raspberry Pi 4 with Ubuntu 24.04 #52

Open
iamskok opened this issue May 22, 2024 · 5 comments

Comments

@iamskok
Copy link

iamskok commented May 22, 2024

Describe the bug
Running docker compose up -d for Unbound DNS on Raspberry Pi 4 with Ubuntu 24.04 results in the error: The futex facility returned an unexpected error code and core dumps.

To Reproduce
Steps to reproduce the behavior:

  1. Docker compose file:
    name: dns_stack
    
    services:
      unbound:
        build:
          context: .
          dockerfile: Dockerfile-unbound
        image: "unbound"
        container_name: "unbound"
        hostname: "unbound_1"
        environment:
          TZ: "UTC"
        ports:
          - "5353:5353/udp"
          - "5353:5353/tcp"
        volumes:
          - "/opt/dns-stack/docker/unbound/opt_unbound_etc_unbound/:/opt/unbound/etc/unbound/"
        command: ["/opt/unbound/etc/unbound/unbound.sh"]
        healthcheck:
          test: ["CMD-SHELL", "drill @127.0.0.1 -p 5353 example.com || exit 1"]
          interval: 1m
          timeout: 10s
          start_period: 10s
          retries: 3
        restart: unless-stopped
  2. Customizations (config files):
    • unbound.sh:
      #!/bin/bash
      mkdir -p /opt/unbound/etc/unbound/dev
      cp -a /dev/random /dev/urandom /dev/null /opt/unbound/etc/unbound/dev/
      mkdir -p -m 700 /opt/unbound/etc/unbound/var
      chown _unbound:_unbound /opt/unbound/etc/unbound/var
      /opt/unbound/sbin/unbound-anchor -a /opt/unbound/etc/unbound/var/root.key
      curl -o /opt/unbound/etc/unbound/root.hints https://www.internic.net/domain/named.cache
      chmod 644 /opt/unbound/etc/unbound/root.hints
      /opt/unbound/sbin/unbound-control-setup
      exec /opt/unbound/sbin/unbound -d -c /opt/unbound/etc/unbound/unbound.conf
    • Dockerfile-unbound:
      FROM mvance/unbound-rpi:1.19.2
      
      RUN apt-get update && \
          apt-get install -y --no-install-recommends curl && \
          rm -rf /var/lib/apt/lists/*
  3. Directory structure:
    /opt/dns-stack/
    ├── docker
    │   └── unbound
    │       └── opt_unbound_etc_unbound
    │           ├── unbound.sh
    │           ├── unbound.conf
    │           └── Dockerfile-unbound
    └── compose.yml
    
  4. Run docker compose up -d
  5. See error

Expected behavior
Unbound DNS service should start without core dumps or errors, and healthcheck should pass.

Error messages

[+] Building 1.7s (5/5) FINISHED                                                      docker:default
 => [unbound internal] load build definition from Dockerfile-unbound                            0.0s
 => => transferring dockerfile: 370B                                                            0.0s
 => [unbound internal] load metadata for docker.io/mvance/unbound-rpi:1.19.2                    0.4s
 => [unbound internal] load .dockerignore                                                       0.0s
 => => transferring context: 2B                                                                 0.0s
 => CACHED [unbound 1/2] FROM docker.io/mvance/unbound-rpi:1.19.2@sha256:4b95a1331a69a60720147  0.0s
 => ERROR [unbound 2/2] RUN apt-get update &&     apt-get install -y --no-install-recommends c  1.2s
------
 > [unbound 2/2] RUN apt-get update &&     apt-get install -y --no-install-recommends curl &&     rm -rf /var/lib/apt/lists/*:
0.466 The futex facility returned an unexpected error code.
0.945 Aborted (core dumped)
------
failed to solve: process "/bin/sh -c apt-get update &&     apt-get install -y --no-install-recommends curl &&     rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 134

Additional context

  • Hardware: Raspberry Pi 4
  • OS: Ubuntu 24.04
  • Docker Image: mvance/unbound-rpi:1.19.2
  • Docker Version: 26.1.3

The same setup worked on Ubuntu 23.10 without issues.

@koseduhemak
Copy link

facing the same problem at the moment with vanilla image and no additional modifications:
Docker Image: mvance/unbound-rpi:1.18.0
OS: Ubuntu 24.04
Docker Version: 26.1.3
Hardware: Raspberry Pi 4

@klaas-sysop
Copy link

klaas-sysop commented May 29, 2024

also the same isue

Docker Image: mvance/unbound-rpi
OS: Ubuntu 24.04
Docker Version: 26.1.3
Hardware: Raspberry Pi 5

EDIT 29/05/2024

I tried mvance/unbound-rpi:1.16.0 and it didnot work. so my next step is trying Ubuntu 23.04

EDIT 30/05/2024

Ubuntu 23.04 works perfectly just as iamskok mentioned

@neryencarnacion
Copy link

I'm facing the same issue!

Docker Image: mvance/unbound-rpi
OS: Ubuntu 24.04
Docker Version: 26.1.4
Hardware: Raspberry Pi 5

@m-ammar
Copy link

m-ammar commented Jun 30, 2024

Any workarounds for this issue? The alternative of downgrading to ubuntu-23.10 is not appealing.

@GreenMonito
Copy link

I have the same problem too

Docker Image: mvance/unbound-rpi
OS: Ubuntu 24.04
Docker Version: 27.0.3, build 7d4bcd8
Hardware: Raspberry Pi 3B+

Is there a solution for this?, downgrading to Ubuntu 23 is not viable

Thank you so much!

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

6 participants