Unable to select Audio Recording device (Docker)

[magnetar]

I just finished installing Rhasspy on Docker (https://rhasspy.readthedocs.io/en/latest/installation/) but have been unable to select my USB webcam as a recording device.

Connecting to the docker container reveals the hardware is detected (hw:3,0):

root@629d4ed389a0:/# arecord -l
**** List of CAPTURE Hardware Devices ****
card 1: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 2: ALC892 Alt Analog [ALC892 Alt Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 3: U0x46d0x8c9 [USB Device 0x46d:0x8c9], device 0: USB Audio [USB Audio]
  Subdevices: 0/1
  Subdevice #0: subdevice #0

But it is not listed in the device dropdown in Rhasspy Settings for Audio Recording.

I checked this link to test recording: https://linuxconfig.org/how-to-test-microphone-with-audio-linux-sound-architecture-alsa which gives:

root@629d4ed389a0:/# arecord -f S16_LE -d 5 -r 16000 --device="hw:3,0" /tmp/test-mic.wav
arecord: main:828: audio open error: Device or resource busy

I’ve tested the microphone on the host and it’s working fine. I’m very stuck. Any help or suggestions would be greatly appreciated!

[fastjack]

Maybe this can help:

Playing sound at the same time from Rhasspy (Docker) and the host

Thank you. With this asound.conf and docker command it works now. But explain me something. Wich parameter in your docker command makes it work? It dosen’t work with mine. docker run -it --name rhasspy \ --restart always \ -v "$HOME/.config/rhasspy/satellite:/profiles" \ -v "/etc/asound.conf:/etc/asound.conf" \ --network host \ --device /dev/snd \ rhasspy/rhasspy --profile de --user-profiles /profiles --local-mqtt-port 13183

[magnetar]

Thanks for pointing me to that. There’s a ton of settings in that asound.conf file that I suspect are specific to that user…

Though I suspect it may have indeed had something to do with the audio output since I disabled the Audio Playing, it seems to now show up as an available recording device and can successfully detect a command.