Skip to content
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

Open
panomitrius opened this issue Dec 20, 2020 · 7 comments
Open

docker container doens't seem to start #7

panomitrius opened this issue Dec 20, 2020 · 7 comments

Comments

@panomitrius
Copy link

panomitrius commented Dec 20, 2020

Running this with the default configuration creates a container but it doesn't seem to work at all. docker ps shows:

CONTAINER ID   IMAGE                                COMMAND                  CREATED              STATUS                          PORTS                                                                      NAMES
33aea0ae60bc   mikebrady/shairport-sync             "/start.sh"              About a minute ago   Up About a minute                                                                                          shairport-sync_shairport-sync_1

docker logs 33aea0ae60bc shows nothing. And when I try to access the docker with a bash-shell it displays:

OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown

I'm running it from Ubuntu 20.04 Server, all packages up to date.

@mikebrady
Copy link
Owner

My guess is that Shairport Sync is starting up and then quitting because something is wrong.

The docker image does not contain bash, but it does contain sh.

@panomitrius
Copy link
Author

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: ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave. Is there any guide to set it up that I can use?

@mikebrady
Copy link
Owner

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.

@panomitrius
Copy link
Author

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..

@mikebrady
Copy link
Owner

Hi there. Just wondering, did you manage to solve this problem?

@panomitrius
Copy link
Author

No, I didn't put any more effort to it..

@mikebrady
Copy link
Owner

Okay, thanks for the response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants