Skip to content

qemu signal 11 crash after 2FA submission on Apple Silicon (linux/amd64) #61

Description

@rasps-limes

Hello. ### I'm unable to complete the initial Apple Music login on an Apple Silicon Mac M2 because the wrapper consistently crashes immediately after the 2FA code is accepted.

Integration context

The wrapper is being used through ALACarte:
https://github.com/sosjalapeno/alacarte

ALACarte uses the wrapper as a Docker service with:

  • platform: linux/amd64
  • Docker Desktop on Apple Silicon
  • Rosetta amd64 emulation

The issue reproduces through the ALACarte login flow, but the crash occurs inside the wrapper process after the 2FA code is detected and submitted.

Environment

  • Host: Apple Silicon Mac (macOS)
  • Docker Desktop
  • Platform: linux/amd64
  • Wrapper version: 1.2.0
  • Repository HEAD:
    8441d68 feat(ui): route offline health pill to settings

Problem

The wrapper consistently crashes during Android runtime initialization.

The web container stays healthy, but the wrapper exits immediately.

Observed output:

[+] starting...
[+] initializing ctx...
__bionic_open_tzdata_path: ANDROID_DATA not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_DATA not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
qemu: uncaught target signal 11 (Segmentation fault) - core dumped

Container status:

Exited (0)

Docker restart count:

0

The wrapper exits with status 0, so Docker does not restart it because restart policy is "on-failure".

What works

  • wrapper --version
  • wrapper --help

Output:

wrapper 1.2.0

The wrapper executable itself appears to be valid.

Compose configuration

Wrapper service:

  • platform: linux/amd64
  • entrypoint: /app/wrapper
  • command:
    -H 0.0.0.0

Volumes:

  • ./data/wrapper:/app/rootfs/data
  • /dev/null:/app/rootfs/dev/null
  • /dev/random:/app/rootfs/dev/random
  • /dev/urandom:/app/rootfs/dev/urandom
  • /dev/zero:/app/rootfs/dev/zero

No docker-compose.override.yml is present.

Image inspection

Inside the image:

/app/rootfs/system/bin/linker64

exists and is executable.

Host file:

wrapper/rootfs/system/bin/linker64

reports:

ELF 64-bit LSB shared object, x86-64, static-pie linked

Tests performed

  1. Clean wrapper state

    • Removed existing wrapper data
    • Created a fresh data/wrapper directory
    • Crash still occurs.
  2. Apple credentials

    • Crash occurs before successful login.
    • Therefore saved credentials/session are not required to reproduce.
  3. Rosetta

    • Tested with Rosetta enabled and disabled.
    • Crash still occurs.
  4. QEMU/binfmt

    • Verified amd64 emulation is available.
    • Crash still occurs.
  5. ANDROID_ROOT / ANDROID_DATA

    • Temporarily set:

      ANDROID_ROOT=/system
      ANDROID_DATA=/data

    Output changed to:

    __bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
    __bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!

    but the wrapper still crashes with:

    qemu: uncaught target signal 11 (Segmentation fault) - core dumped

Conclusion

The wrapper binary itself works (help/version).

The crash occurs only after Android runtime initialization begins.

The problem reproduces with:

  • clean wrapper state
  • latest source
  • wrapper 1.2.0
  • linux/amd64 container
  • Apple Silicon Docker Desktop

The issue appears to be inside the Android runtime used by the wrapper (or its interaction with amd64 emulation on Apple Silicon), rather than the Docker Compose configuration, Apple credentials, or wrapper state.

I am using the officially supported Apple Silicon path: Docker Desktop amd64 emulation via Rosetta. The wrapper reaches Apple 2FA successfully, reads the code file, then crashes with QEMU signal 11 immediately after submitting the code.

Question

Is this a known issue with Apple Silicon / Rosetta / QEMU?

Is there an updated wrapper/rootfs or a workaround for Apple Silicon Macs?

I'm happy to test patches or provide additional logs if needed.

Thank you!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions