Cantinarr
Container
Media requests and server management in one app. Household members browse and request movies, shows, books, and music, follow downloads, and get notified when content is ready. Administrators manage Radarr, Sonarr, Chaptarr, Lidarr, and download clients, review approvals, and investigate stuck downloads. AI is optional, and authorized MCP clients can use the same server. GitHub: windoze95/cantinarr
Image details
Source details
Configuration
TypeContainerlinuxghcr.io/windoze95/cantinarr:latest8585:8585/tcp/config : /portainer/Files/AppData/Cantinarr/configCANTINARR_PUSH_GATEWAY_URL=https://push.cantinarr.comCANTINARR_ARR_CALLBACK_URL=unless-stoppedNotes
Standalone Install
Select an install method, to see config/commands for deploying Cantinarr
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select Cantinarr, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
More install options in our documentation, or see windoze95/cantinarr for app-specific guidance.
Cantinarr
Self-hosted media requests and server management.
Website · Documentation · Live demo
Cantinarr lets your household and friends browse and request movies, TV shows, ebooks, audiobooks, and music. Administrators manage requests, libraries, and download clients from the same app. It connects to Radarr, Sonarr, Chaptarr, Lidarr, and more.
Preview
Features
- Movie, season, ebook, audiobook, and album requests with approvals and per-user limits.
- Live availability, download progress, and Discord or push (free for the foreseeable future) notifications.
- Library and download queue management across multiple service instances.
- Plex, Jellyfin, Emby, and Audiobookshelf account access and playback links.
- Connect links, passkeys, Plex sign-in, and OpenID Connect.
- Kids accounts with movie and TV rating limits.
- An optional AI agent for finding media, making requests, and admin troubleshooting, plus supervised repairs for persistent download problems.
- An MCP server and a Seerr-compatible API for external tools.
Getting started
Run the server with Docker, Unraid, or a Linux binary, then follow the setup guide to connect your services and invite your household.The web app is included. Mobile apps connect to your server and are available in beta:
- iPhone and iPad: TestFlight
- Android: Google Play
Documentation
Community
Join Discord for help and discussion. Report bugs on GitHub or suggest and vote on features on the roadmap.Pull requests are welcome. See the contributor guide and repository instructions. You can support development through GitHub Sponsors.
License
AGPL-3.0. Copyright (c) 2026 Julian Dice.This product uses the TMDB API but is not endorsed or certified by TMDB.
Serve Cantinarr on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying cantinarr.example.com to http://cantinarr:8585
Add this to your Caddyfile
cantinarr.example.com {
reverse_proxy http://cantinarr:8585
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs cantinarr - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:8585 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :8585 - Stop the other service, or pick a different host port. In
8585:8585only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:8585. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, cantinarr can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 8585
Permission denied on volumes
If the logs show "permission denied", the app can't write to its data folder on the host.
- Fix the ownership:
sudo chown -R 1000:1000 /portainer/Files/AppData/Cantinarr/config
Image won't pull
Test the pull directly on the host: docker pull ghcr.io/windoze95/cantinarr:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64, arm64 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect cantinarr --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Required settings are blank
CANTINARR_ARR_CALLBACK_URL has no default value, and cantinarr may crash or misbehave if left empty.
- Fill it in on the deploy screen before hitting deploy.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue on windoze95/cantinarr
- Template not working: Open an issue within the template's repo
- This website not working: Open an issue on lissy93/portainer-templates
A single container
Cantinarr runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.
The app image
An image is the app packed up ready to go, everything Cantinarr needs bundled into one download. This template pulls ghcr.io/windoze95/cantinarr:latest, which Docker fetches once (about 182 MB) and then starts your own copy from.
Where the image comes from
Docker pulls its images from registries, public libraries of ready-built apps. Cantinarr's comes from the GitHub Container Registry, published by windoze95.
Version tags
The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Pin a specific tag if you would rather stay on one version.
Which machines it runs on
Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.
Ports
A port is the door the app answers on. A mapping like 8585:8585 means it's reachable on port 8585 of your server, where the left number is yours to change and the right one belongs to the app. It opens:
8585:8585
Volumes
A volume is where Cantinarr keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/configfrom/portainer/Files/AppData/Cantinarr/configon the host
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Cantinarr takes 2 of them, and one needs a value before it'll start properly:
CANTINARR_PUSH_GATEWAY_URL, defaults tohttps://push.cantinarr.com. Push gateway for the companion iOS and Android apps. The server enrolls itself on first start; clear to disable push, or point it at your own gateway.CANTINARR_ARR_CALLBACK_URL, needs a value. Origin your Radarr, Sonarr, and Chaptarr containers POST webhooks back to, for example http://192.168.1.10:8585. Leave blank to use whatever address you browse to. This is not the address people reach Cantinarr at; set that in the app under Settings, External Address. Formerly named CANTINARRPUBLICURL, which existing containers can keep using.
Restart policy
The restart policy here is unless-stopped, so Docker restarts Cantinarr after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).
Networking
Nothing custom is set, so Cantinarr sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.
Container name
Once it's deployed, Portainer names the container cantinarr. That's what you'll spot in the containers list and use in commands like docker logs cantinarr.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Open source license
Cantinarr is open source, released under the AGPL-3.0 license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Cantinarr up. Add the template list to Portainer once, then deploying Cantinarr is a click rather than a wall of config.



