​​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​​

​Htpcmanager is a front end for many htpc related applications.

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 ghcr.io/linuxserver/htpcmanager 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:

Usage

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

docker-compose (recommended)

Compatible with docker-compose v2 schemas.

---
version: "2.1"
services:
  htpcmanager:
    image: ghcr.io/linuxserver/htpcmanager
    container_name: htpcmanager
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
    volumes:
      - /path/to/appdata/config:/config
    ports:
      - 8085:8085
    restart: unless-stopped

docker cli

docker run -d \
  --name=htpcmanager \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/London \
  -p 8085:8085 \
  -v /path/to/appdata/config:/config \
  --restart unless-stopped \
  ghcr.io/linuxserver/htpcmanager

Parameters

Docker 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.

Ports (-p)

Environment Variables (-e)

Volume Mappings (-v)

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)

Application Setup

The webui is found at port 8085. Smartmontools and psutil have not been included, you can safely ignore the warning error in the log.

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

• To monitor the logs of the container in realtime:

  • docker logs -f htpcmanager

• Container version number

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

• Image version number

  • docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/linuxserver/htpcmanager

Versions

• 26.10.20: - Rebase to alpine 3.12, python3, change upstream project

• 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.

• 16.01.19: - Add pipeline logic and multi arch.

• 17.08.18: - Rebase to alpine 3.8.

• 12.12.17: - Rebase to alpine 3.7.

• 20.07.17: - Internal git pull instead of at runtime.

• 25.05.17: - Rebase to alpine 3.6.

• 07.02.17: - Rebase to alpine 3.5.

• 14.10.16: - Add version layer information.

• 26.09.16: - Add back cherrypy after removal from baseimage.

• 10.09.16: - Add layer badges to README.

• 28.08.16: - Add badges to README.

• 08.08.16: - Rebase to alpine linux.

• 14.01.15: - Remove hardcoded loglevel from the run command, set in webui

• 19.09.15: - Initial Release.