13

I'm using various docker containers which, under the covers are built on Debian sid. These images lack /dev/snd and /dev/snd/seq, which pretty much makes sense since they have no hardware audio card.

Several pieces of software I'm using to generate MIDI files require these sequencer devices to be present. They're not necessarily used to send out audio, but the code itself dies in init if the sound devices do not exist. To be clear, I don't need to generate an audio signal within docker, rather I just need these to exist to make other software happy.

So far, what I've tried is endlessly installing various alsa packages (alsa-utils, alsa-oss, and others) and trying to modprobe my way out of this, all with no luck.

Within a docker container, what needs to happen to have valid audio devices even if dummy?

FrobberOfBits
  • 17,634
  • 4
  • 52
  • 86
  • 1
    I was setting up google home in a docker container on a rasberrypi running raspbian couple weeks back. Even after installing the sound drivers (alsa-utils) google home just would not start if I dont plugin a sound device. You already understand this going by your question. All I can say is may be there is no other way :( – Swarup Donepudi Sep 14 '17 at 03:32
  • 1
    See if this helps. You need to mount the `/dev/snd` from host https://blog.jessfraz.com/post/docker-containers-on-the-desktop/ – Tarun Lalwani Sep 14 '17 at 10:06
  • @TarunLalwani I've seen references to `--device /dev/snd` elsewhere, but this guidance is from 2015, and the official docker docs don't mention that --device is a valid option, I think this was deprecated/removed. – FrobberOfBits Sep 14 '17 at 11:45
  • Doesn't `--device /dev/snd/seq:/dev/snd/seq` work? – CL. Sep 14 '17 at 12:11
  • @FrobberOfBits, who says its not there in documentation? Please check https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities – Tarun Lalwani Sep 14 '17 at 12:27
  • Sorry -- my mistake; --device is documented, but still isn't helpful when bridging with Mac OS X, because it uses CoreAudio. Need to dig further on that https://stackoverflow.com/questions/14867033/which-dev-devices-are-the-microphone-and-speaker-in-mac-os-x – FrobberOfBits Sep 14 '17 at 12:31
  • Note that bridging to my host OS's sound hardware isn't strictly necessary. I don't need sound output, I only need to make software happy which expects that capability – FrobberOfBits Sep 14 '17 at 12:31
  • this certainly is solvable since I have installed ubuntu on my mac as a dual boot and sound ran fine – Scott Stensland Sep 14 '17 at 14:11
  • Have you tried this? https://stackoverflow.com/questions/40136606/how-to-expose-audio-from-docker-container-to-a-mac – code Sep 23 '17 at 08:26
  • Also, and this might be the last option, you can install Ubuntu (or any other linux distro) in VirtualBox and then work on your Docker shenanigans inside that VM? Since, Ubuntu will have access to your Mac's Audio, and since it is Ubuntu so it can bridge its audio(which is technically, your Mac's) to the docker container, I believe it might solve your problem. – code Sep 23 '17 at 08:28
  • @AbhishekSoni I appreciate the suggestion; I can manage to get audio bridged to a mac, but this isn't really a workable solution, because it requires modifying the host OS. The objective isn't to bridge audio, it's to make the software that requires the device happy. This may work for a mac host, but the point of doing this in docker is so that it can be deployed elsewhere, and I can't modify the host OS everywhere I go, nor will the host OS always be running Mac OS X. – FrobberOfBits Sep 23 '17 at 13:05
  • How are you connecting the sequencer devices to your mac? Perhaps if they're connected via usb you could share the `/dev/bus/usb` to the docker container and it could have its own software to interpret the usb device as the audio device it needs. – pale bone Sep 24 '17 at 14:04
  • 2
    I think this has been solved. If all you need is the directories, just mount them as volumes to some other directory that exists on the host. https://stackoverflow.com/questions/28985714/run-apps-using-audio-in-a-docker-container – mttdbrd Sep 24 '17 at 18:50
  • Inside of your Dockerfile, what happens when you call `touch /dev/snd`? How about if you instead make a dummy character device, for example by using `mknod /dev/snd c 89 1`? If these commands do no work, then what errors do they raise? – Nick Settje Sep 03 '18 at 09:36

1 Answers1

1

I've had success getting sound through Docker (not the same problem, I know) by adding the devices whe running the container.

docker run -it --device /dev/snd myimage

The permissions can get challenging very quickly, you might want to try initially using --device /dev/snd along with --privileged and then dial back privileges little by little once it works.

rexypoo
  • 1,697
  • 1
  • 6
  • 10