I’m testing a scenario where I run Plexamp as a headless application inside a Docker container and then access it through my web browser for music playback. While the Plex web interface functions correctly, I prefer using the Plexamp interface, but currently, the browser doesn’t play any audio when using Plexamp in this configuration. Can anyone provide insights or suggest workarounds for this issue? Thanks in advance.
hey charlie, i had a simlar issue. enabling pulseaod in my container fixed audio bridging for the browser. check your docker config for audio drivers. hope its helpfull.
I encountered a similar problem with headless configurations in a containerized environment. My solution involved not only enabling the necessary audio drivers but also verifying that the Docker container had proper access to the host’s audio system. At times, the issue was rooted in permission settings, which required an adjustment in how the container interfaces with the audio hardware. I recommend double-checking your Docker runtime options and ensuring that your audio devices are correctly mounted and available to the container.
In my experience setting up a headless Plexamp setup, the device didn’t initially show any audio because the container wasn’t configured to interact properly with the host’s audio system, even though I didn’t use PulseAudio as a primary workaround. I resolved it by adjusting the container’s ALSA configuration and ensuring that permissions for the sound devices were explicitly allowed. Double-checking these configurations can solve the issue, and in my case, it made a significant difference for browser-based audio playback.