Public | Automated Build

Last pushed: a year ago
Short Description
Short description is empty for this repo.
Full Description


This is a Docker container for AirSonos.

AirSonos exposes Sonos as an AirPlay endpoint. To learn more about AirSonos, read the author's blog about it.


There isn't really any installation, but you need to have Docker installed. Consult the official Docker documentation for full details.

Running the airsonos container

The first run will pull the container image down to your local machine.

sudo docker run -d --restart=always --net="host" --name="airsonos" \
  -p 5000-5050:5000-5050/tcp justintime/airsonos

Notes on running the container

Because the discovery mechanism uses mdns, you have to use --net="host" in order for discovery of your Sonos devices to work properly. Since AirSonos binds to random ports between 5000 and 5050, it's best to publish them all.

Docker Pull Command
Source Repository

Comments (12)
18 days ago

I was able to get this working on a Synology by following these instructions

Use host networking and give it your LAN broadcast address in the second step if necessary. I was actually able to launch this successfully without step 2 (patch sonos.js) or 3 (patch helper.js), but I did step 2 anyway. I don't even have a helper.js, so I didn't edit it.

I hope this helps someone. I was pretty excited to get this working so I can drop the dedicated VM I have for running Airsonos. 👍

3 months ago

On the "Image" Tab klick on Start. On the "Advances Settings" select the "Network" Tab. Check the Option "User same Network like the docker host".

Finshed. Delete all aother containers

3 months ago

Hi I am new to using docker on Synology. I had airsonos working then I did a system update and I also added a sub, now the version running on my Synology does not see any of my Sonos devices. if I run the airsonos app one my Mac it does see them? can anyone help me please - who is running airsonos on Synology with latest updates on symbology and latest updates to sonos system. thanks

6 months ago

I always got the Error Message "timeout: down: dbus: 0s, normally up, want up" after "Searching for Sonos devices on network...". and no Devices will be found. Does anyone know what´s going wrong here?

[root@localhost ~]# docker run --restart=always --net=host -p 5000-5050:5000-5050/tcp justintime/airsonos
Running /etc/my_init.d/
No SSH host key available. Generating one...
Creating SSH2 RSA key; this may take some time ...
Creating SSH2 DSA key; this may take some time ...
Creating SSH2 ECDSA key; this may take some time ...
Running /etc/my_init.d/
Running /etc/rc.local... Booting runit daemon...
* Runit started as PID 78
ok: run: dbus: (pid 89) 0s
ok: run: avahi: (pid 88) 0s
Searching for Sonos devices on network...

timeout: down: dbus: 0s, normally up, want up
timeout: down: dbus: 1s, normally up, want up
timeout: down: dbus: 1s, normally up, want up
timeout: down: dbus: 1s, normally up, want up
timeout: down: dbus: 1s, normally up, want up

a year ago

created to pull in fixes in master

2 years ago

Disregard my last comment, tried the leachbj/airsonos image and it is working now.

2 years ago

I’ve changed the default DSM ports, but when I attempt to use this from iTunes, I get an error “An unknown error occurred (-15000). Thoughts?

2 years ago

Thanks gr8m8sam. This works great indeed but if you stop and start the container it does not work anymore (I assume this is due to the option net=host that is not passed then) any idea how to make this restart resistant without having to delete the container after each restart ... ? thanks !

2 years ago

SSH into the Synology and run

docker run -d --restart=always --net="host" --name="airsonos" -p 5000-5050:5000-5050/tcp justintime/airsonos

2 years ago

Thanks a lot Justin for making this Docker container.
Works fine on DSM 5.2 + Docker. Just changed the default DSM login ports 5000 to 4000. You will find the setting under Control Panel>Network>DSM Setting.
Grate works guys. Keep it up.