docker-airsonos
docker-airsonos copied to clipboard
not working in ios 9
Hello, Airsonos not working anymore with ios 9 so your build too :( Could you update your build if eventually airsonos start working with ios 9 ? Thanks
Sure thing. For those who come looking, here's the AirSonos issue link: https://github.com/stephen/airsonos/issues/177
Looks like there is a new airsonos build available compatible with ios 9 et raspberry pi. Do you know when you'd be able to update the container? https://github.com/stephen/nodetunes/issues/1
+1
I pushed up a new testing docker image with the changes we need for ALAC, but I'm not in a spot where I was able to do any testing at all. @lennvilardi and @xonbul, if you could pull down that image and test it, and report back your findings, it would help tremendously. Specifically, there's two things to test:
- Make sure iOS 9 works
- Make sure that we didn't have a regression where speakers are being listed more than once
You can pull down the testing image by doing a docker pull justintime/airsonos:testing
docker pull justintime/airsonos:testing testing: Pulling from justintime/airsonos
150ee130d88c: Pull complete 78dfa2695df9: Pull complete d59faf7dd6c7: Pull complete 5d4979b85e30: Pull complete 5b97f45ef78b: Pull complete 0242f8d4f205: Pull complete e467aa44b2a2: Pull complete f8aabfbc746c: Pull complete 8981ba64415b: Pull complete 511136ea3c5a: Already exists 6170bb7b0ad1: Already exists 9cd978db300e: Already exists a6d44c263269: Already exists 13e42d0c2a51: Already exists 846e143f3fab: Already exists 10ebd1d649cb: Already exists 5db917407faa: Already exists 745d3ac92697: Already exists Digest: sha256:fb23d124d8457f6ae5267a3d0178ef7202c01bd773062f4736b5acda47d0f353 Status: Downloaded newer image for justintime/airsonos:testing
docker run -d --restart=always --net="host" --name="airsonostest" -p 50 00-5050:5000-5050/tcp justintime/airsonos:testing e6d6e597618b773f7fb63c4db39d2e2d0b1a78e0e39fc167d249480c3a018d41
No Airsonos in the Airplay view :( (I'm running ios 9.1 on an iphone 6s plus)
I'll see what I can do, but wow, the Airsonos project is in pretty bad shape. I can't get an executable that starts from either building from source, or using NPM. I've even tried going back a couple versions, and still had problems. Check out the issue queue at Airsonos -- the whole project is in a broken state right now, and the author hasn't responded yet to any of the issues regarding the problem.
I'm not a Node developer at all, so I doubt I'll be able to fix this until Stephen (or a nodejs developer) fixes things up.
I went ahead and created an issue over at https://github.com/stephen/airsonos/issues/231 to track this.
Just tried @leachbj new docker image referenced in https://github.com/stephen/airsonos/issues/231#issuecomment-150714329 and looks to be working. Thanks @leachbj!
https://hub.docker.com/r/leachbj/airsonos/ (various forks are on github https://github.com/leachbj/docker-airsonos).
Working on ios9.02/ios9.1 on a xpenology DSM 5.2 on a ts140 on a ESXI VM
- Pulled @leachbj's docker: "docker pull leachbj/airsonos"
- Opened up Synology Docker to delete the old/existing airsonos images/containers
- SSH into Diskstation and ran the following "docker run -d --restart=always --net="host" --name="airsonos" -p 5000-5050:5000-5050/tcp leachbj/airsonos"
- Do the happy dance!
Thanks again for the great work!
Thanks you so much :) it works for me too
Unfortunately, https://github.com/leachbj/docker-airsonos is no go on Raspberry PI 2 :( docker run -d --restart=always --net="host" --name="airsonos" -p 5000-5050:5000-5050/tcp leachbj/airsonos a7b1d391e92b0eb39d39967ce36f1c67e2ed078b543a0887fee7b1b86ac7b48c FATA[0000] Error response from daemon: Cannot start container a7b1d391e92b0eb39d39967ce36f1c67e2ed078b543a0887fee7b1b86ac7b48c: [8] System error: exec format error
@xonbul not really sure what that error means - according to https://github.com/stephen/nodetunes/issues/1 a newer version of node and overclocking helps with the Rasberry PI but that talks about performance not just your error.
@leachbj would you prefer to maintain your own project, or would you rather I pull in your fixes?
Sent you a few PRs with the main changes. With those two you should have the same as mine (other than nodetunes updates on the microadam fork).
I've pulled in the fixes and that triggered a build on DockerHub. While airsonos does run, at least for me, it doesn't find any of my Sonos devices. I've got some uncommon circumstances that I can't go into that may be causing me issues that no one else would have, so I'd appreciate feedback on whether it works or not for others.
I just tried that one on the DS412; justintime/airsonos latest 09396485b2cb 17 hours ago 590.7 MB Unfortunately, no joy. I can't see any of my devices in the airplay list.
The output from the two was slightly different, with your image it just enumerates the rooms like; Setting up AirSonos for Office {192.168.0.16:1400} with my image it looks like; Office (@ 192.168.0.16:1400, RINCON_B8E99999999C01400:33) .. Search complete. Set up 4 device tunnels.
Just wanted to share that the docker container works for me with iOS 9 when building the docker image myself using the latest airsonos master. I had to fix one tiny detail to make docker build actually succeed: #5