Philip Peterson 855f5dbded fix VNC pid exhaustion: remove bluez loop, raise machine.slice limit ... kded5 was activating org.bluez.obex in a tight loop (no BT hardware in container), spawning thousands of obexd threads until the libpod scope hit its TasksMax=9286 systemd default — causing fork failures and a 502. - vnc-desktop/Dockerfile: purge bluez/bluez-obexd and delete D-Bus service activation files so kded5 can't trigger the loop - linux.nix: machine.slice TasksMax=infinity so the libpod scope ceiling can't be hit by legitimate KDE thread counts - linux.nix: containers.conf pids_limit=0 (unlimited) to let podman pass TasksMax=infinity to new container scopes pids.current went from 9286 (exhausted) to 159 after the fix. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>		2026-05-25 19:53:28 -08:00
..
Dockerfile	fix VNC pid exhaustion: remove bluez loop, raise machine.slice limit	2026-05-25 19:53:28 -08:00
start.sh	fix riverside DNS, VNC stale lock, and pids limit	2026-05-25 19:36:36 -08:00