While there is the option to run something like Multipass or VirtualBox with a custom provisioning script for Docker and then configure shared folders, I was looking for a drop-in replacement with minimal or no configuration.Ĭolima fits the criteria well.
It makes a request to every time the settings are opened, even with anonymous reporting turned off.Weekly tips and anonymous reporting are enabled by default.Pop-ups asking me how likely I am to recommend Docker Desktop to a co-worker.It’s a quick and easy way to get Docker running on macOS.Īlthough technically it works fine, the following reasons made me look for a replacement: It runs the daemon in a VM, handles port-forwarding, shared folders and sets up the Docker CLI.
You don't have to use a host volume to accomplish this- you could also do a 'docker cp', or even COPY it into an image.Replacing Docker Desktop for Mac with Colima home Replacing Docker Desktop for Mac with Colima December 21, 2021ĭocker Desktop for Mac is probably the most commonly used solution to run Docker on macOS. I was able to play sound from a container running on my docker-for-mac via pulseaudio.Īs long as you get the ~/.config/pulse/cookie file to appear in the correct location, you should be able to play sound. The HOME environment variable is necessary so paplay can find the same ~/.config/pulse/cookie file. The PULSE_SERVER environment variable is the en0 IP address of my OSX host, so paplay knows what to connect to. The second is because both the client and the server need to have a copy of the same ~/.config/pulse/cookie file (per that archlinux wiki guide). The first is the fact that my cockatiel.wav is located inside $HOME.
What this does is run a container with my local home directory as a volume. Next, I ran the pulseaudio client in a container like this: docker run -rm -v $HOME:$HOME -w $HOME -it \ I still have sound with those changes to default.pa, so I'm satisfied that my changes didn't break anything. the pulseaudio daemon seems to start on demand, and passes its complaints back to paplay to be printed on my screen if I made a typo. I reran paplay cockatiel.wav on my mac to make sure my changes still worked. I edited /usr/local/Cellar/pulseaudio/9.0/etc/pulse/default.pa on my mac, and uncommented the following two lines: load-module module-esound-protocol-tcp
I was able to adapt it to this situation by doing the following. I found the following guide on the Archlinux Wiki discussing setting up pulseaudio network sound: I found jess/pulseaudio, which appears to be intended to be a pulseaudio server, but I should be able to use it as a client as well. My next step is to find an image that has a copy of paplay. I was able to verify this worked by running the following, hearing sound come out of my speakers: paplay cockatiel.wav
I was able to get pulseaudio installed and working on OSX with the following command: brew install pulseaudio By contrast, a virtualbox or vmware fusion VM does have the ability to do passthrough audio. The Docker-for-Mac VM doesn't have any sound passthrough device, so there isn't anything that you could take advantage of from that angle.