Docker image for a Spotify Connect endpoint.

This is based on LibreSpot.

This is useful in the following scenarios:

1. you are a hobbyist and you want to turn a small appliance connected to speakers into a Spotify Connect receiver (typically a raspberry pi)
2. that's it :-)

• multi-architecture:
  • linux/amd64
  • linux/arm64
• hardened:
  • image runs read-only
  • image runs with no capabilities but NET_BIND_SERVICE
  • process runs as a non-root user, disabled login, no shell
• lightweight
  • based on our slim Debian Bullseye
  • simple entrypoint script
  • multi-stage build with no installed dependencies dependent on the following for the runtime image:
    • libpulse0
    • libasound2
• observable
  • healthcheck
  • log to stdout
  • prometheus endpoint

unsupported (probably builds - but I lost interest):

• linux/arm/v7
• linux/arm/v6
• linux/386
• linux/ppc64le
• linux/s390x

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 Spotify

You 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 endpoint

Of course using any privileged port for that would require CAP_NET_BIND_SERVICE.

See DEVELOP.md