Portainer Templates logo

Portainer Templates

Daapd Daapd

Container

Music

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

Image details

Pulls: 7.6M
Architecture: amd64, arm64
Image size: 67 MB
Latest: 28.10.20250118
User: linuxserver
Created: Sep 17, 2016
Updated: 1 years ago
Status: active

Configuration

Type
Container
Platform
linux
Image
linuxserver/daapd:latest
Volumes
/config : /portainer/Files/AppData/Config/Daapd/music : /portainer/Music
Env vars
PUID=1000PGID=100
Restart
unless-stopped

Template by mikestraney

Standalone Install

Select an install method, to see config/commands for deploying Daapd

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Daapd, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation.

linuxserver.io
Blog Discord Discourse Fleet GitHub Open Collective
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

DEPRECATION NOTICE

This image is deprecated. We will not offer support for this image and it will not be updated.
We recommend switching to the official container image https://github.com/owntone/owntone-container

linuxserver/daapd

Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build LSIO CI
Daapd (iTunes) media server with support for AirPlay devices, Apple Remote (and compatibles), Chromecast, MPD and internet radio.
daapd

Supported Architectures

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:latest 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:
ArchitectureAvailableTag
x86-64amd64-\
arm64arm64v8-\
armhf

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. The default credentials are admin/changeme.
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

To help you get started creating a container from this image you can either use docker-compose or the docker cli.
>!NOTE >Unless a parameter is flaged as 'optional', it is mandatory and a value must be provided.

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

---
services:
  daapd:
    image: lscr.io/linuxserver/daapd:latest
    container_name: daapd
    network_mode: host
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - /path/to/daapd/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=Etc/UTC \
  -v /path/to/daapd/data:/config \
  -v /path/to/music:/music \
  --restart unless-stopped \
  lscr.io/linuxserver/daapd:latest

Parameters

Containers 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.
ParameterFunction
--net=hostShares host networking with container.
-e PUID=1000for UserID - see below for explanation
-e PGID=1000for GroupID - see below for explanation
-e TZ=Etc/UTCspecify a timezone to use, see this list.
-v /configWhere daapd server stores its config and dbase files.
-v /musicMap to your music folder.

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__MYVAR=/run/secrets/mysecretvariable

Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable 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 your_user as below:
id your_user

Example output:
uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)

Docker Mods

Docker Mods Docker Universal 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:
```bash
docker exec -it daapd /bin/bash
```
  • To monitor the logs of the container in realtime:
```bash
docker logs -f daapd
```
  • Container version number:
```bash
docker inspect -f '{{ index .Config.Labels "build_version" }}' daapd
```
  • Image version number:
```bash
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/daapd:latest
```

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 (noted in the relevant readme.md), 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 images:
* All images:

    ```bash
    docker-compose pull
    ```

* Single image:

    ```bash
    docker-compose pull daapd
    ```
  • Update containers:
* All containers:

    ```bash
    docker-compose up -d
    ```

* Single container:

    ```bash
    docker-compose up -d daapd
    ```
  • You can also remove the old dangling images:
```bash
docker image prune
```

Via Docker Run

  • Update the image:
```bash
docker pull lscr.io/linuxserver/daapd:latest
```
  • Stop the running container:
```bash
docker stop daapd
```
  • Delete the container:
```bash
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:
```bash
docker image prune
```

Image Update Notifications - Diun (Docker Image Update Notifier)

>!TIP >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 x8664 hardware and vice versa using lscr.io/linuxserver/qemu-static
docker run --rm --privileged lscr.io/linuxserver/qemu-static --reset

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

Versions

  • 17.01.25: - Deprecate.
  • 27.08.24: - Rebase to Alpine 3.20.
  • 20.03.24: - Rebase to Alpine 3.19.
  • 25.08.23: - Rebase to Alpine 3.18, remove abandoned libspotify libs.
  • 05.07.23: - Deprecate armhf. As announced here
  • 23.02.23: - Rebase to Alpine 3.17, migrate to s6v3.
  • 31.05.22: - Make sure the user has access to the audio device.
  • 31.05.22: - Add new deps, flex and bison.
  • 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 X8664 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 cpucore 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.

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs daapd
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:100 /portainer/Files/AppData/Config/Daapd (and the same for the other mapped folders)
  • Or set the PUID and PGID variables (defaults 1000:100) to match your own user, found with id $USER

Image won't pull

Test the pull directly on the host: docker pull linuxserver/daapd:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect daapd --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

Daapd runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Daapd needs bundled into one download. This template pulls linuxserver/daapd:latest, which Docker fetches once (about 67 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Daapd's comes from Docker Hub, published by linuxserver.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 28.10.20250118. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Volumes

A volume is where Daapd keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /config from /portainer/Files/AppData/Config/Daapd on the host
  • /music from /portainer/Music on the host

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Daapd takes 2 of them, all with defaults you can leave alone or tweak:

  • PUID, defaults to 1000
  • PGID, defaults to 100

Restart policy

The restart policy here is unless-stopped, so Docker restarts Daapd after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Users and permissions

The PUID and PGID settings tell it which user and group to act as on your host. Point them at your own account (find yours with id $USER) so the files it writes into your mounted folders come out owned by you rather than root.

Networking

Nothing custom is set, so Daapd sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container daapd. That's what you'll spot in the containers list and use in commands like docker logs daapd.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Daapd up. Add the template list to Portainer once, then deploying Daapd is a click rather than a wall of config.