Make PulseAudio readiness mean a live connection, clear stale socket state

The pulse_socket named volume survives container recreation, so after a
compose recreate the previous container's /run/pulse/pid and native
socket were still present. PulseAudio read the stale pid file, decided a
daemon was already running, and refused to start:

    E: [pulseaudio] pid.c: Daemon already running.

The entrypoint still reported "PulseAudio socket ready" because it only
checked that the socket file existed - and a stale one did. Capture then
failed in a restart loop against a dead daemon.

Readiness in both the op25 entrypoint and drb-edge-node now means a
pactl probe actually succeeds. Stale pid/socket are removed only when
that probe fails, so a live daemon's socket is never deleted.

pulseaudio-utils was missing from the edge-node image (only libpulse0
was installed), so no pactl binary existed there at all - added.

Capture exits are now classified: a missing source logs at ERROR and
names the configured PULSE_SOURCE, rather than looking identical to
"daemon not up yet". Retrying forever against a wrong source name is how
the April PulseAudio failure stayed hidden.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

This commit is contained in:

Logan Cusano

2026-08-04 22:10:28 -04:00

parent b0a8ed2a5a

commit 7c4a3f2f20

6 changed files with 402 additions and 54 deletions

									
										drb-edge-node/Dockerfile
									
		+1
		
												View File
												
				@@ -5,6 +5,7 @@ RUN apt-get update && apt-get install -y \

				    libopus0 \

				    libopus-dev \

				    libpulse0 \

				    pulseaudio-utils \

				    && rm -rf /var/lib/apt/lists/*

				WORKDIR /app