The LinuxServer.io team brings you another container release featuring:

• regular and timely application updates
• easy user mappings (PGID, PUID)
• custom base image with s6 overlay
• weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
• regular security updates

Find us at:

• Blog - all the things you can do with our containers including How-To guides, opinions and much more!
• Discord - realtime support / chat with the community and the team.
• Discourse - post on our community forum.
• Fleet - an online web interface which displays all of our maintained images.
• GitHub - view the source for all of our repositories.
• Open Collective - please consider helping us by either donating or contributing to our budget

linuxserver/daapd

Daapd (iTunes) media server with support for AirPlay devices, Apple Remote (and compatibles), Chromecast, MPD and internet radio.

Supported Architectures

Our images support multiple architectures such as x86-64, arm64 and armhf. We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling lscr.io/linuxserver/daapd should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Application Setup

Map your music folder, open up itunes on the same LAN to see your music there.

The web interface is available at http://<your ip>:3689

For further setup options of remotes etc, check out the daapd website, Owntone.

Enable spotify connect server

Enable the spotify connect server by creating a pipe named 'spotify' in the root of your mounted music folder (not possible on most network mounts):

mkfifo <music_folder>/spotify

The spotify connect server should show up as the 'forked-daapd' device in your Spotify application.

It is recommended to set the pipe_autostart option to true in your forked-daapd config.

Usage

Here are some example snippets to help you get started creating a container.

docker-compose (recommended, click here for more info)

---
version: "2.1"
services:
  daapd:
    image: lscr.io/linuxserver/daapd
    container_name: daapd
    network_mode: host
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
    volumes:
      - <path to data>:/config
      - <path to music>:/music
    restart: unless-stopped

docker cli (click here for more info)

docker run -d \
  --name=daapd \
  --net=host \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/London \
  -v <path to data>:/config \
  -v <path to music>:/music \
  --restart unless-stopped \
  lscr.io/linuxserver/daapd

Parameters

Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

Environment variables from files (Docker secrets)

You can set any environment variable from a file by using a special prepend FILE__.

As an example:

-e FILE__PASSWORD=/run/secrets/mysecretpassword

Will set the environment variable PASSWORD based on the contents of the /run/secrets/mysecretpassword file.

Umask for running applications

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.

User / Group Identifiers

When using volumes (-v flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id user as below:

  $ id username
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)

Docker Mods

We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.

Support Info

• Shell access whilst the container is running: docker exec -it daapd /bin/bash
• To monitor the logs of the container in realtime: docker logs -f daapd
• container version number
  • docker inspect -f '{{ index .Config.Labels "build_version" }}' daapd
• image version number
  • docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/daapd

Updating Info

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.

Below are the instructions for updating containers:

Via Docker Compose

• Update all images: docker-compose pull
  • or update a single image: docker-compose pull daapd
• Let compose update all containers as necessary: docker-compose up -d
  • or update a single container: docker-compose up -d daapd
• You can also remove the old dangling images: docker image prune

Via Docker Run

• Update the image: docker pull lscr.io/linuxserver/daapd
• Stop the running container: docker stop daapd
• Delete the container: docker rm daapd
• Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
• You can also remove the old dangling images: docker image prune

Via Watchtower auto-updater (only use if you don't remember the original parameters)

• Pull the latest image at its tag and replace it with the same env variables in one run:

  docker run --rm \
  -v /var/run/docker.sock:/var/run/docker.sock \
  containrrr/watchtower \
  --run-once daapd

• You can also remove the old dangling images: docker image prune

Note: We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.

Image Update Notifications - Diun (Docker Image Update Notifier)

• We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.

Building locally

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone https://github.com/linuxserver/docker-daapd.git
cd docker-daapd
docker build \
  --no-cache \
  --pull \
  -t lscr.io/linuxserver/daapd:latest .

The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static

docker run --rm --privileged multiarch/qemu-user-static:register --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

Versions

• 12.02.22: - Rebase to Alpine 3.15.
• 14.09.21: - Enabled librespot. Disabled spotify on ARMv7
• 10.07.21: - Change of paths to work with the new package name, OwnTone.
• 02.04.21: - Update upstream repo, again.
• 30.03.21: - Update upstream repo.
• 06.10.20: - Enabled Spotify on Alpine 3.12 for X86_64 and ARMv7.
• 01.06.20: - Rebasing to alpine 3.12.
• 16.01.20: - Rebase to alpine linux 3.11 and build antlr3c from source.
• 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
• 14.01.19: - Add pipeline logic and multi arch.
• 20.08.18: - Rebase to alpine linux 3.8.
• 09.06.18: - Use buildstage and update dependencies.
• 05.03.18: - Use updated configure ac and disable avcodecsend to hopefully mitigate crashes with V26.
• 25.02.18: - Query version before pull and build latest release.
• 03.01.18: - Deprecate cpu_core routine lack of scaling.
• 07.12.17: - Rebase to alpine linux 3.7.
• 03.12.17: - Bump to 25.0, cpu core counting routine for faster builds, linting fixes.
• 26.05.17: - Rebase to alpine linux 3.6.
• 06.02.17: - Rebase to alpine linux 3.5.
• 10.01.17: - Bump to 24.2.
• 14.10.16: - Add version layer information.
• 17.09.16: - Rebase to alpine linux, remove redundant spotify support, move to main repository.
• 28.02.16: - Add chromecast support, bump dependency versions.
• 04.01.16: - Disable ipv6 by default because in v23.4 it doesn't work in unraid with it set.
• 17.12.15: - Add in spotify support.
• 25.11.15: - Initial Release.