audioserve killed by SIGSYS on Raspbian 11

[uGeek]

I have mounted the docker on my vps with arm64 and it works perfectly, but for Raspberry of arm64, it doesn't work.
Great job being able to have this image for arm architecture.

Thank you very much

[srd424]

Have you got any error messages / logs that might clue me in a bit? What version of Raspbian, docker, etc?

[srd424]

(FWIW, I run on a Raspberry Pi, but I use podman, might be worth a try. I will dig mine out and double-check the latest version runs OK on it.)

[uGeek]

In the logs it appears:

Attaching to audioserve
audioserve exited with code 159

I am using docker-compose

[srd424]

Interesting - exit code 159 implies killed by signal 31, which is SIGSYS (unknown system call) on ARM. You could try passing --privileged to docker run and seeing if that helps? Syscall filtering can be problematic, particularly on ARM which IIRC uses syscalls for things like memory barriers, at least on 32 bit.

What version of Raspbian? (lsb_release -a should tell you.)

[srd424]

According to docker/compose#123 (comment), you can enable privileged mode in docker compose like this:

version: "3"

services:
  audioserve:
    image: ghcr.io/srd424/audioserve-docker:v0.22.0
    restart: unless-stopped
    command: --tags /audiobooks
    privileged: true
    environment:
      - "AUDIOSERVE_SHARED_SECRET=VGM4oDS6wGKge9"
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - "./config:/home/audioserve/.audioserve"
      - "/path/to/Audio/Books:/audiobooks"

[uGeek]

You're right!!! Giving it privileges as you indicate works perfectly.

Thanks a lot. And thank you very much for your time and contribution to the audioserve project to make it work on ARM64.

I recommend that you put this docker-compose example in the README.md

[uGeek]

Raspbian version:

No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye

[srd424]

Well, ideally it shouldn't need privileges, so that's still one to try to get to the bottom of, but less urgent now if it solves your immediate problem!