[BUG] jemalloc is never loaded when NET_ADMIN/NET_RAW are added

Aperta
#150 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker, linux

Direzione di ricerca

Start with the svc-homeassistant/run script mentioned in the issue and trace both capability branches, including where setcap runs and how Home Assistant is launched. The report gives an ambient-capability capsh example to compare with the current setup; verify behavior in a rebuilt image with and without Bluetooth capabilities, then confirm jemalloc is mapped in /proc/<pid>/maps in both cases.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Is there an existing issue for this?
  • I have searched the existing issues
Current Behavior

AI disclosure: I found and diagnosed this with an AI assistant (Claude Code). The commands and output below were run on my own Pi, and I've reviewed the report before posting.

svc-homeassistant/run exports LD_PRELOAD=/usr/local/lib/libjemalloc.so.2, but when the container has NET_ADMIN + NET_RAW (as the readme suggests for Bluetooth), the same script first runs setcap on the python binary. A binary with file capabilities runs in secure-execution mode (AT_SECURE=1), and the musl loader ignores LD_PRELOAD in that mode. So Home Assistant silently runs on musl's malloc and MALLOC_CONF does nothing.

In the running container the variable is set, but the library is not mapped:

$ P=$(docker top homeassistant -o pid,args | awk '/python3 -m homeassistant/{print $1}')
$ sudo tr '\0' '\n' < /proc/$P/environ | grep LD_PRELOAD
LD_PRELOAD=/usr/local/lib/libjemalloc.so.2
$ sudo grep -c jemalloc /proc/$P/maps
0

/etc/ld.so.preload isn't a workaround: musl doesn't support it,

Expected Behavior

jemalloc is loaded whether or not the Bluetooth capabilities are enabled, as the run script intends.

Possible fix: grant the capabilities as ambient capabilities instead of file capabilities. Ambient caps don't trigger secure-execution mode, so LD_PRELOAD keeps working. In the repro below, the process ends up with the same effective set (CapEff: 0000000000003400: net_bind_service, net_admin, net_raw) and still runs as abc. Roughly:

exec \
    s6-notifyoncheck -d -n 60 -w 5000 -c "nc -z localhost 8123" \
    capsh --caps="cap_net_raw,cap_net_admin,cap_net_bind_service+eip cap_setpcap,cap_setuid,cap_setgid+ep" \
        --keep=1 --user=abc --addamb=cap_net_raw,cap_net_admin,cap_net_bind_service \
        -- -c "exec python3 -m homeassistant -c /config"

The no-Bluetooth branch would need the same treatment with only cap_net_bind_service, since it also runs setcap. I've tested the mechanism, not a rebuilt image with this run script.

Steps To Reproduce

This uses a copy of busybox in place of python, so it doesn't need the full init:

docker run --rm --cap-add NET_ADMIN --cap-add NET_RAW --entrypoint bash \
  lscr.io/linuxserver/homeassistant:latest -c '
id abc >/dev/null 2>&1 || adduser -D -u 911 abc
J=/usr/local/lib/libjemalloc.so.2; mkdir /tmp/x; B=/tmp/x/busybox; cp /bin/busybox $B
echo -n "no file caps:   "; LD_PRELOAD=$J s6-setuidgid abc $B grep -c jemalloc /proc/self/maps
setcap cap_net_raw,cap_net_admin=+ep $B
echo -n "file caps:      "; LD_PRELOAD=$J s6-setuidgid abc $B grep -c jemalloc /proc/self/maps
setcap -r $B
echo -n "ambient caps:   "; LD_PRELOAD=$J capsh \
  --caps="cap_net_raw,cap_net_admin,cap_net_bind_service+eip cap_setpcap,cap_setuid,cap_setgid+ep" \
  --keep=1 --user=abc --addamb=cap_net_raw,cap_net_admin,cap_net_bind_service \
  -- -c "$B grep -c jemalloc /proc/self/maps"'

Output (a count of 0 means jemalloc is not loaded):

no file caps:   3
file caps:      0
ambient caps:   3
Environment
- OS: Debian 12 (bookworm), Raspberry Pi 5 Model B 8GB
- How docker service was installed: Docker's official apt repo (docker-ce 29.8.2)
CPU architecture

arm64

Docker creation
homeassistant:
  image: lscr.io/linuxserver/homeassistant:latest   # 2026.10.4-ls260
  network_mode: host
  environment:
    - PUID=1000
    - PGID=1000
    - TZ=Europe/London
  volumes:
    - ./config:/config
    - /var/run/dbus:/var/run/dbus:ro
  cap_add:
    - NET_ADMIN
    - NET_RAW
  restart: unless-stopped
Container logs
[migrations] started
[migrations] no migrations found
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: 2026.10.4-ls260
Build-date: 2026-10-24T23:03:55+00:00
───────────────────────────────────────
**** New container detected, fixing python package permissions. This may take a while. ****
Setting permissions
[custom-init] No custom files found, skipping...
Adding cap_net_admin and cap_net_raw to python binary for bt access
[... custom integration warnings omitted ...]
Connection to localhost (::1) 8123 port [tcp/*] succeeded!
[ls.io-init] done.

Note: there is no error to show. The loader drops LD_PRELOAD silently; the relevant line is "Adding cap_net_admin and cap_net_raw to python binary for bt access".
Lingua principale
Dockerfile
Stelle
285
Fork
34
Merge medio
41m
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di linuxserver/docker-homeassistant

Tutte le issue di linuxserver/docker-homeassistant

Issue simili

Altre issue su Backend & API Design

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.