Open Camotoy opened 3 weeks ago
Same error here "s6-supervise airconnect: warning: unable to spawn"
Running via UnRaid on intel hardware.
Thank you for reporting. Looks like I'm seeing too. I'll have to dig into this. Odd that it's a permissions based issue it seems. Probably something changed in the base image. I'll have to do some research. For the moment I'll have to see if I can revert my latest back and hold the automated build until I can fix this manually. Short term, as noted - please use the previous version tag.
Work was bit hectic, but I've got a temporary fix in build right now. Issue is something to do with changes in base image I was using from LSIO. Have to dig into that but don't have the time at the moment, so I've put in this temp fix by pinning to previous release of their image which should be available for a bit. Will drop into their discord to see how I can fix it.
@Flyinace2000 @Camotoy I've had to restructure a bit so there is possibility for a lot of unknown scenarios I'd already accounted for in my previous version since this is a totally different S6 setup. Can you please take a stab at testing out the dev
branch of the container on Docker hub? Try with different devices, modifications, etc if you can just to help me validate it's working properly now. My first initial test seemed to run properly - but I don't pass any arguments, modify, etc.
as far as i can tell the dev branch is working. There is a bug in ios 18 that has issues with airplay 1. that will hopefully get fixed in the next beta, so i can't test end to end. I can see the mdns broadcast be sent out, and everything binds correctly, plus the binary for aircast is running correctly. Proxmox, lxc container, running ubuntu 22.04.4, using a docker deployment
@jacoknapp thanks for the report. Ya I have the same issue running iOS 18 beta. Had to use my MacBook not running beta to validate. 😄
I did notice higher CPU usage in the dev version, like it's not taking a full core in the lxc container I have dedicated for this.
Interesting - I might have to create another branch to test that pulls an older version of the airconnect app, but uses the new run format. I can't imagine adjusting my s6 usage should be causing that large of a difference - but I think comparing with an older version of the airconnect app is only true way to see if its the container or the app. i'll get back to this, but might take a week or so to jump back into.
Just picking this back up, now that the beta is fixed. It does appear to be use 1 core while just idle. Which is weird, but running this for a while and haven't seen this before.
Thanks for checking back in. Good news, the latest
tag should put you back into the current working version. I've gotta get some time to run a test pushing the old airconnect version into the new container format I'm using. Find out if it's airconnect or its my container. Will update here once I get it checked out.
Hello!
Docker logs when running from the latest tag appear as such:
Run command:
docker run --name "airconnect" -d --net=host --restart unless-stopped 1activegeek/airconnect
1.7.0 works fine.
I'm no Docker expert so I apologize if I did something wrong! I did note the image on Dockerhub was recently updated.