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/tautulli

Tautulli is a python based web application for monitoring, analytics and notifications for Plex Media Server.

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

Version Tags

This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.

Application Setup

Access the webui at <your-ip>:8181, for more information check out Tautulli. To use the build-in Plex LogViewer you have to add a volume, preferably ReadOnly. Then in tautulli gui settings, under Plex Media Server, turn on Show Advanced and set the Logs Folder to the folder you mapped.

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:
  tautulli:
    image: lscr.io/linuxserver/tautulli:latest
    container_name: tautulli
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - <path to data>:/config
    ports:
      - 8181:8181
    restart: unless-stopped

docker cli (click here for more info)

docker run -d \
  --name=tautulli \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -p 8181:8181 \
  -v <path to data>:/config \
  --restart unless-stopped \
  lscr.io/linuxserver/tautulli:latest

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 tautulli /bin/bash
• To monitor the logs of the container in realtime: docker logs -f tautulli
• container version number
  • docker inspect -f '{{ index .Config.Labels "build_version" }}' tautulli
• image version number
  • docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/tautulli: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 (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 tautulli
• Let compose update all containers as necessary: docker-compose up -d
  • or update a single container: docker-compose up -d tautulli
• You can also remove the old dangling images: docker image prune

Via Docker Run

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

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

• 22.06.23: - Revert master branch to Alpine 3.17 due to issues with Python 3.11.
• 25.05.23: - Rebase to Alpine 3.18, deprecate armhf.
• 15.12.22: - Rebase master branch to Alpine 3.17.
• 04.10.22: - Rebase master branch to Alpine 3.16, migrate to s6v3.
• 10.01.22: - Rebase to Alpine 3.15.
• 11.07.21: - Add curl package.
• 23.01.21: - Rebasing to alpine 3.13.
• 11.07.20: - Add py3-openssl.
• 05.06.20: - Rebasing to alpine 3.12. Rework to python3.
• 12.04.20: - Added mock from pip and donate links.
• 19.12.19: - Rebasing to alpine 3.11.
• 28.06.19: - Rebasing to alpine 3.10.
• 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
• 22.02.19: - Rebasing to alpine 3.9.
• 26.01.19: - Add pipeline logic and multi arch.
• 23.10.18: - Update plex logs info in readm.
• 16.08.18: - Rebase to alpine 3.8.
• 10.03.18: - Rebrand to tautulli.
• 12.12.17: - Rebase to alpine 3.7.
• 21.07.17: - Internal git pull instead of at runtime.
• 12.07.17: - Add inspect commands to README, move to jenkins build and push.
• 25.05.17: - Rebase to alpine 3.6.
• 20.04.17: - Add pycryptodomex pip package.
• 07.02.17: - Rebase to alpine 3.5.
• 09.09.16: - Add layer badges to README.
• 27.08.16: - Add badges to README.
• 08.08.16: - Rebase to alpine linux.
• 16.07.15: - Inital Release.