Any idea why this might not work within a Docker container? I can play and record from multiple applications at the same time outside of Docker (which indicates to me that my
dsnoop config is working), but then when I try to play back a file from the host and from within the Rhasspy container at the same time, I get an error from
root@1530daa229ed:/usr/lib/rhasspy-voltron# aplay etc/wav/beep_hi.wav ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave aplay: main:828: audio open error: Device or resource busy
Is the Docker container is trying to grab the hardware device and create an entirely new
dmix plugin instance within the container instead of using the existing one outside of the container?
I’ve tried linking my
/etc/asoundrc.conf into the container, making
/dev/snd/ available in the container, and even setting the container to
privileged without any success.
This is on a Pi Zero so I’d rather not run
pulseaudio and hog more CPU…
Any advice would be appreciated! Thanks!