简体中文
English
Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is hotio.dev?
hotio.dev is documentation for a collection of Docker container images maintained by a developer known as hotio. Rather than being an app itself, it is a hub that explains how to run self-hosted media and automation software in Docker.
The catalog is organized into three groups:
- Base – a shared foundation image (
hotio/base) that other images build on. - Apps – ready-made images for popular self-hosted tools, including Plex, Jellyfin, Sonarr, Radarr, Lidarr, Bazarr, Prowlarr, Jackett, qBittorrent, SABnzbd, NZBGet, Tautulli, and Duplicacy.
- Scripts – helper utilities such as SysInfo, Pullio, and Arr Discord Notifier.
Most app pages include Docker CLI or Compose examples, so the site is aimed at people who already run a Docker host—typically a home server or NAS—and want consistent, prebuilt images instead of assembling their own. The documentation also points to a Discord server for questions, and mentions GitHub Sponsors, Open Collective, and Bitcoin for donations, though no pricing is stated.
If you are choosing between image maintainers, check whether the image you need is listed, whether its documentation matches your Docker or Compose setup, and whether the update and support workflow suits you. A practical next step is to open the page for the specific app you want to run and follow its example configuration.
How do I install a hotio Docker image using Docker CLI or Docker Compose?
Start by picking the image you need from the hotio collection, then run it with either the Docker CLI or a Compose file. The site's home page itself is a hub: it links to per-app pages (for example hotio/jellyfin, hotio/sonarr, hotio/radarr, hotio/qbittorrent, hotio/plex, hotio/bazarr, hotio/jackett, hotio/sabnzbd, hotio/nzbget) and notes that most images come with Docker CLI or Compose examples. Those per-app pages are where the actual commands live, so the practical first step is to open the page for your chosen app rather than guessing flags from the home page.
Docker CLI
The general pattern for a hotio image follows standard Docker usage:
docker run -d \
--name=appname \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Etc/UTC \
-p 8080:8080 \
-v /path/to/config:/config \
--restart unless-stopped \
hotio/appname
Replace appname with the image you want and adjust the port, volume paths, and environment variables to match that app's documentation. The PUID/PGID and TZ variables are common in this style of media-server image; the exact set for your app is listed on its own page.
Docker Compose
Compose is usually easier to maintain because the configuration lives in a file you can version and edit:
services:
appname:
image: hotio/appname
container_name: appname
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /path/to/config:/config
ports:
- 8080:8080
restart: unless-stopped
Then start it with docker compose up -d from the directory containing the file.
Which to choose
| Situation | Better fit |
|---|---|
| Quick test of one container | Docker CLI |
| Multiple related apps (media stack) | Compose |
| Rebuilding or moving hosts | Compose (file is portable) |
| One-off debugging with extra flags | Docker CLI |
Practical next step
Open the specific app's page on hotio.dev, since that is where the maintainer publishes the exact CLI and Compose examples, including the correct volume mount points and ports for that application. If you get stuck, the site points to a Discord server for support, and it also lists GitHub Sponsors, Open Collective, and Bitcoin as donation options — none of which are required to use the images.
A useful decision rule: if you plan to run more than two or three of these containers together, start with Compose from the beginning. It avoids the drift that creeps in when you hand-edit long docker run commands, and it makes the whole stack reproducible when you move to new hardware.
Which hotio Docker images are available for media automation apps like Sonarr, Radarr, and Plex?
hotio.dev documents a set of Docker images that cover most of the common media-automation stack. The page lists them by category, so the fastest approach is to pick the app you want and use its image name directly.
Media automation and related apps listed
| Purpose | Image |
|---|---|
| TV series management | hotio/sonarr |
| Movie management | hotio/radarr |
| Media server | hotio/plex, hotio/jellyfin |
| Indexer management | hotio/prowlarr |
| Usenet downloader | hotio/sabnzbd, hotio/nzbget |
| Torrent client | hotio/qbittorrent, hotio/rflood |
| Subtitle management | hotio/bazarr |
| Request management | hotio/requestrr, hotio/seerr |
| Media organization | hotio/unpackerr |
| Stats and monitoring | hotio/tautulli |
| Music management | hotio/lidarr |
| Other automation | hotio/autoscan, hotio/jackett, hotio/nzbhydra2, hotio/prowlarr |
The site also groups images under Base, Apps, and Scripts, and includes supporting images such as hotio/base, hotio/caddy, hotio/cloudflareddns, hotio/duplicacy, hotio/mergerfs, hotio/qbitmanage, hotio/qui, hotio/slskd, hotio/stash, hotio/whisparr, and hotio/doplarr.
Next step
Open the page for the exact app you need and follow its Docker CLI or Compose example, since most images come with one. If you are building a full stack, start with the download client and indexer images first, then add Sonarr, Radarr, and Plex or Jellyfin once those are reachable.
For official documentation on the individual applications themselves, see Sonarr, Radarr, and Plex.
What are the hotio/base and hotio/mergerfs images used for?
hotio/base and hotio/mergerfs serve different purposes: the first is a foundation for other containers, the second is a working container in its own right for combining drives.
hotio/base
hotio/base is the shared base image that the project's application images are built on top of. It isn't something you normally run directly. Its value is consistency: because the application containers derive from the same base, they share a common underlying environment, which makes behaviour and configuration more predictable across images.
Use it as a starting point if you are building your own image and want it to match the conventions of the hotio containers, rather than as a standalone service.
hotio/mergerfs
hotio/mergerfs packages mergerfs, the union filesystem tool that presents multiple disks or mount points as a single pooled directory. It appears in the project's Apps list, so it is intended to be deployed as a container.
Typical use is a media or storage server where several drives hold content but you want one path to read from and write to. Instead of juggling mount points, you point applications at the pooled path. On its own it does not add redundancy — if a drive fails, the data on that drive is still lost — so it is usually paired with a parity or backup layer rather than treated as protection.
How to choose
- Building or customising a container that should match the hotio ecosystem: start from
hotio/base. - Combining several drives into one namespace for apps like download clients or media servers: deploy
hotio/mergerfs.
As a next step, open the documentation for each image and read its Docker CLI or Compose example — the site states that most images include one. That example shows the required mounts and paths, which is where mergerfs setups usually go wrong.
Related images documented alongside these include hotio.dev entries such as hotio/plex, hotio/sonarr and hotio/qbittorrent. If you have questions after reading the examples, the project points to its Discord server for support.
How can I get support for hotio Docker images if I run into problems?
For help with any hotio Docker image, the main route is the project's Discord server, which the site links from its Support section. That is where the maintainer and other users discuss configuration problems, container errors and general troubleshooting for the images listed on hotio.dev.
The site itself is documentation first: each app page (for example the entries for hotio/qbittorrent, hotio/radarr or hotio/sonarr) is meant to get you started with docker cli or compose examples. So before asking, it is worth checking the relevant app page and the FAQ section — many "it won't start" or "where do I put this variable" questions are answered by the example compose file matching your image.
A practical order of operations
- Reproduce the problem and capture the full container log, not just the last line.
- Compare your compose file against the example on that image's page.
- Check the FAQ page for common pitfalls.
- If it still fails, ask on Discord with the image name and tag, your compose snippet (redact secrets), the host OS and the complete error output.
That detail matters because these are community-supported images rather than a paid support product. The site does mention GitHub Sponsors, Open Collective and Bitcoin donations, but those are funding channels, not a support contract — do not expect a guaranteed response time.
If your issue turns out to be with the underlying application rather than the container packaging, the upstream project's own community is usually the better place; for example, Jellyfin and Plex both run their own forums. Keep the container-specific question (volumes, permissions, environment variables, tags) on Discord, and the app-behaviour question upstream.
What are the Pullio, SysInfo, and Arr Discord Notifier scripts on hotio.dev used for?
These three scripts are companion utilities for people running hotio's Docker images for self-hosted media apps (Plex, Sonarr, Radarr, qBittorrent and similar). They handle maintenance and notification chores that sit around the containers rather than being an app themselves.
Pullio — keeps images current. It checks for updated versions of your containers and pulls them, so you are not manually watching for new tags. The practical trade-off: automatic updates are convenient but can surprise you if an upstream release changes behavior, so many users schedule it and keep an eye on release notes.
SysInfo — a diagnostic helper. It gathers system and container information you would otherwise assemble by hand when asking for help, which is why it pairs naturally with the project's Discord support channel.
Arr Discord Notifier — bridges your *arr apps to Discord. Instead of checking each app's interface, you get activity and status updates pushed into a Discord channel you already watch.
Which one do you need?
| Goal | Script |
|---|---|
| Stop manually updating containers | Pullio |
| Collect system/container details for troubleshooting | SysInfo |
| Get app activity pushed to Discord | Arr Discord Notifier |
Start with Pullio if updates are your pain point, and add the Arr Discord Notifier if you want visibility without opening each app. Setup instructions and compose examples live alongside the individual image pages at hotio.dev, and questions are handled in the project's Discord server linked from that site.
Cloudflare
Fastly
User reviews (0)