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:

Discord - realtime support / chat with the community and the team.
IRC - on freenode at #linuxserver.io. Our primary support channel is Discord.
Blog - all the things you can do with our containers including How-To guides, opinions and much more!
Podcast - on hiatus. Coming back soon (late 2018).

linuxserver/htpcmanager

Htpcmanager is a front end for many htpc related applications. Hellowlol version.

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

Architecture	Tag
x86-64	amd64-latest
arm64	arm64v8-latest
armhf	arm32v6-latest

Usage

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

docker

docker create \
  --name=htpcmanager \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/London \
  -p 8085:8085 \
  -v </path/to/appdata/config>:/config \
  --restart unless-stopped \
  linuxserver/htpcmanager

docker-compose

Compatible with docker-compose v2 schemas.

---
version: "2"
services:
  htpcmanager:
    image: 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

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.

Parameter	Function
`-p 8085`	Application WebUI
`-e PUID=1000`	for UserID - see below for explanation
`-e PGID=1000`	for GroupID - see below for explanation
`-e TZ=Europe/London`	Specify a timezone to use EG Europe/London.
`-v /config`	Configuration files.

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 has not been included, you can safely ignore the warning error in the log.

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" }}' linuxserver/htpcmanager

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 Run/Create

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

Via Taisun auto-updater (especially useful 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 shot:

docker run --rm \
-v /var/run/docker.sock:/var/run/docker.sock taisun/updater \
--oneshot htpcmanager

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

Via Docker Compose

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

Versions

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.