Docker image for a Spotify Connect endpoint.
This is based on LibreSpot.
This is useful in the following scenarios:
unsupported (probably builds - but I lost interest):
The following is the most straight-forward example, using host networking:
docker run -d --rm \
--name "spot" \
--env "MOD_MDNS_NAME=Super Name For Your Spotify Connect Endpoint" \
--volume /tmp \
--group-add audio \
--device /dev/snd \
--net host \
--cap-drop ALL \
--read-only \
docker.io/dubodubonduponey/spotify
You need to run this in host
or mac(or ip)vlan
networking (because of mDNS).
Any additional arguments when running the image will get fed to the librespot
binary.
This is specifically relevant if you need to select a different alsa device, card or mixer, or use another librespot option.
Here is an example:
docker run -d --rm \
--name "spot" \
--env "MOD_MDNS_NAME=Super Name For Your Spotify Connect Endpoint" \
--volume /tmp \
--group-add audio \
--device /dev/snd \
--net host \
--cap-drop ALL \
--read-only \
docker.io/dubodubonduponey/spotify \
--device default:CARD=Mojo \
--enable-volume-normalisation \
-v
For a reference of all librespot options, try:
docker run --rm \
docker.io/dubodubonduponey/spotify \
--help
You may specify the following environment variables at runtime:
MOD_MDNS_NAME
(eg: Totale Croquette
) controls the "name" under which your endpoint will appear in SpotifyYou can also tweak the following for control over which internal ports are being used:
PORT
(eg: 10042
) controls the port used by the http command endpointOf course using any privileged port for that would require CAP_NET_BIND_SERVICE
.
See DEVELOP.md