search

wernight / docker-mopidy

Containerized Mopidy MPD (Music Player Daemon) along with Spotify, Google Music... plugins.
https://hub.docker.com/r/wernight/mopidy/
MIT License
160 stars 86 forks source link

Spotify client not found #24

Open tdelesio opened 5 years ago

tdelesio commented 5 years ago

I'm trying to get this up and running in docker-compose. My file looks like:

  mopidy:
    container_name: mopidy
    image: wernight/mopidy
    volumes:
    - /mnt/storage/appdata/mopidy/local:/var/lib/mopidy/local
    - /mnt/storage/appdata/mopidy/config:/var/lib/mopidy/.config/
    ports:
    - 6600:6600
    - 6680:6680
#    network_mode: host
    devices:
    - /dev/snd:/dev/snd

After the container starts, I go into the config file and manually add the spotify username/password. When the container starts it look like everything is working great. 

mopidy    | INFO     Starting Mopidy mixer: SoftwareMixer
mopidy    | INFO     Starting Mopidy audio
mopidy    | INFO     Starting Mopidy backends: YouTubeBackend, StreamBackend, M3UBackend, FileBackend, SpotifyBackend
mopidy    | INFO     Audio output set to "autoaudiosink"
mopidy    | INFO     Creating dir /var/lib/mopidy/.cache/mopidy/spotify
mopidy    | INFO     Creating dir /var/lib/mopidy/.local/share/mopidy/spotify
mopidy    | INFO     Starting Mopidy core
mopidy    | INFO     Starting Mopidy frontends: MpdFrontend, HttpFrontend
mopidy    | INFO     MPD server running at [::ffff:127.0.0.1]:6600
mopidy    | INFO     HTTP server running at [::ffff:127.0.0.1]:6680
mopidy    | INFO     Starting GLib mainloop
mopidy    | INFO     Logged in to Spotify in online mode

But when I open up spotify on the lan, I do not see the the client in my list. What am I doing wrong? Also is there a way to name the instance manually?

Thanks for the help

wernight commented 5 years ago

Could be that it needs to be added to https://github.com/wernight/docker-mopidy/blob/master/Dockerfile#L24-L30. I didn't check how Spotify client gets installed.