-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker container doens't seem to start #7
Comments
My guess is that Shairport Sync is starting up and then quitting because something is wrong. The docker image does not contain |
That was it, yes. Now it starts, and shows up among the airplay devices. Although when I connect to it I now get this error message: |
If you are starting the docker image as suggested, this message would seem to indicate that there is no default ALSA device available. On a standard Ubuntu systems there would be; I don't know about the server edition. |
Alright.. |
Hi there. Just wondering, did you manage to solve this problem? |
No, I didn't put any more effort to it.. |
Okay, thanks for the response. |
Running this with the default configuration creates a container but it doesn't seem to work at all.
docker ps
shows:docker logs 33aea0ae60bc
shows nothing. And when I try to access the docker with a bash-shell it displays:I'm running it from Ubuntu 20.04 Server, all packages up to date.
The text was updated successfully, but these errors were encountered: