简体中文
EnglishWhat is hotio.dev?
Updated
hotio.dev is the documentation site for the Docker images maintained by hotio. It is not a hosting service or a paid product — it is a reference site that explains what each image is and how to run it. If you are looking for a containerized version of a media, download, or utility app and want to know the correct image name and a working starting configuration, this is the place to look.
What the site covers
The site organizes its images into three main groups, plus a set of helper scripts.
Containers
| Category | What it contains | Examples from the site |
|---|---|---|
| Base | The shared foundation image other images build on | hotio/base |
| Apps | The individual application images | hotio/autoscan, hotio/bazarr, hotio/caddy, hotio/cloudflareddns, hotio/doplarr, hotio/duplicacy, hotio/jackett, hotio/jellyfin, hotio/lidarr, hotio/mergerfs, hotio/nzbget, hotio/nzbhydra2, hotio/plex, hotio/prowlarr, hotio/qbitmanage, hotio/qbittorrent, hotio/qui, hotio/radarr, hotio/requestrr, hotio/rflood, hotio/sabnzbd, hotio/seerr, hotio/slskd, hotio/sonarr, hotio/stash, hotio/tautulli, hotio/unpackerr, hotio/whisparr |
| Scripts | Supporting tooling referenced by the images | SysInfo, Pullio, Arr, Discord Notifier |
The Apps list is the practical part for most visitors: it maps a familiar application name (Sonarr, Radarr, Plex, qBittorrent, and so on) to the exact image path you would pull.
Scripts
The Scripts section covers utilities that sit alongside the containers rather than being apps themselves:
- SysInfo — system information reporting
- Pullio — image update pulling
- Arr — helper for the *arr family of apps
- Discord Notifier — sends notifications to Discord
These are documented separately because they are used with the images rather than deployed as standalone applications.
How you actually use it
The site states that most images come with docker cli or compose examples. That means for a given app you can expect to find a ready-to-adapt command or a compose snippet rather than having to guess at environment variables and volume mounts.
The general workflow is:
- Pick your application from the Apps list (for example
hotio/sonarr). - Open that image's page.
- Copy the provided docker cli or compose example.
- Adjust the paths, ports, and environment values to match your own setup.
- Start the container and confirm it comes up.
The expected result is a running container built from the documented image, using a configuration the maintainer has already validated as a starting point.
Getting help and supporting the project
- Support: The site directs users to join its Discord server for questions.
- Donations: If you want to support the work, the site lists three routes — becoming a GitHub Sponsor, contributing to Open Collective, or sending Bitcoin.
- Affiliate links: The homepage also has an Affiliate Links section.
When this site is the right resource
Use hotio.dev if you already know which application you want to run in Docker and need the correct image reference plus a working example configuration. It is a documentation hub, so it will not provision anything for you — you still need your own Docker host and you still need to adapt the examples to your environment.
If you are instead trying to decide which app to run, or you need help with Docker itself rather than with these specific images, the site's own scope stops at documenting the images; the Discord server is the stated channel for questions that go beyond the docs.