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.
• Discussions - post on our community forum.
• GitHub - view the source for all of our repositories.
• Open Collective - please consider helping us by either donating or contributing to our budget

linuxserver/audiosilo

AudioSilo is a self-hosted audiobook server. Point it at your audiobook folders and listen from the built-in web player or the AudioSilo apps for iOS and Android, with listening progress synced across devices.

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/audiosilo: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:

Architecture	Available	Tag
x86-64	✅	amd64-<version tag>
arm64	✅	arm64v8-<version tag>

Application Setup

On first start AudioSilo creates an admin account and prints its password, plus an auth code for pairing devices, to the container log once, so check the log straight away (docker logs audiosilo).

The server listens on HTTPS with a self-signed certificate by default. Open https://<your-ip>:8080/admin, accept the certificate warning, sign in as admin, and add /audiobooks as a library. The web player is at /web. To connect a phone, enter the auth code on the page at /; it then shows the QR code the AudioSilo app scans.

Settings live in the admin console under Server > Settings, saved to /config/config.yaml. To run behind a reverse proxy such as SWAG, either proxy to the HTTPS port as is, or set HTTPS mode to Off (then restart the container) and let the proxy terminate TLS. Either way, set Public address to the proxied URL so invite links and pairing QR codes point there, and add the proxy's address to Trusted proxies so rate limiting sees your visitors' real addresses.

Any AUDIOSILO_* environment variable overrides its setting and shows as locked in the admin console. See the configuration reference for the full list.

Strict reverse proxies

This image uses a self-signed certificate by default. This naturally means the scheme is https. If you are using a reverse proxy which validates certificates, you need to disable this check for the container.

Read-Only Operation

This image can be run with a read-only container filesystem. For details please read the docs.

Non-Root Operation

This image can be run with a non-root user. For details please read the docs.

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 flagged as 'optional', it is mandatory and a value must be provided.

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

---
services:
  audiosilo:
    image: lscr.io/linuxserver/audiosilo:latest
    container_name: audiosilo
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - /path/to/audiosilo/config:/config
      - /path/to/audiobooks:/audiobooks:ro
    ports:
      - 8080:8080
    restart: unless-stopped

docker cli (click here for more info)

docker run -d \
  --name=audiosilo \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -p 8080:8080 \
  -v /path/to/audiosilo/config:/config \
  -v /path/to/audiobooks:/audiobooks:ro \
  --restart unless-stopped \
  lscr.io/linuxserver/audiosilo: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.

Parameter	Function
-p 8080:8080	Web player, admin console and the API the apps connect to.
-e PUID=1000	for UserID - see below for explanation
-e PGID=1000	for GroupID - see below for explanation
-e TZ=Etc/UTC	specify a timezone to use, see this list.
-v /config	Persistent config files, database, backups and TLS certificates.
-v /audiobooks:ro	Audiobooks location, read-only (the server never writes to your books). Add it as a library in the admin console.
--read-only=true	Run container with a read-only filesystem. Please read the docs.
--user=1000:1000	Run container with a non-root user. Please read the docs.

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

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 audiosilo /bin/bash

• To monitor the logs of the container in realtime:

  docker logs -f audiosilo

• Container version number:

  docker inspect -f '{{ index .Config.Labels "build_version" }}' audiosilo

• Image version number:

  docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/audiosilo: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:

    docker-compose pull

  • Single image:

    docker-compose pull audiosilo

• Update containers:

  • All containers:

    docker-compose up -d

  • Single container:

    docker-compose up -d audiosilo

• You can also remove the old dangling images:

  docker image prune

Via Docker Run

• Update the image:

  docker pull lscr.io/linuxserver/audiosilo:latest

• Stop the running container:

  docker stop audiosilo

• Delete the container:

  docker rm audiosilo

• 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

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-audiosilo.git
cd docker-audiosilo
docker build \
  --no-cache \
  --pull \
  -t lscr.io/linuxserver/audiosilo:latest .

The ARM variants can be built on x86_64 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

• 09.10.26: - Initial Release.