I run portainer as part of my Docker management setup. This is the detailed operating note for why I use it, how I think about it, how it connects to the rest of the lab, and what I would check when it starts acting wrong.
Table of Contents
What this container does
Portainer is the visual control panel for Docker. It shows containers, volumes, images, networks, logs, and stack state from the browser.
The container image is portainer/portainer-ce:latest. I document that on purpose because the image tells me where updates come from, what documentation to trust, and what project probably changed if the container starts behaving differently after an update.
Why I use Portainer
I use it because not every Docker check needs to be a CLI session. It is faster for browsing state and good for teaching what is running.
The deeper reason I use containers for this is control. I want every service to have a defined job, defined storage, defined network exposure, and a clear recovery path. If I cannot explain why a container exists, what data it owns, and what depends on it, then the stack becomes clutter instead of infrastructure.
How I set it up
- Run Portainer as a dedicated management container.
- Persist its data in a volume.
- Mount the Docker socket so it can inspect and manage Docker.
- Expose the admin UI only where it should be reachable.
The setup pattern is always the same in spirit: the container should be disposable, but the data should not be. The app image can be pulled again. The configuration, media library, database state, workflow history, or uploaded files are the pieces that need to survive.
Docker install shape
This is the public-safe version of the setup shape. It shows the image, port idea, and persistent folders without exposing real secrets, private tokens, API keys, claim strings, or provider credentials.
Portainer can control Docker, so expose it carefully and protect access.
services:
portainer:
image: portainer/portainer-ce:latest
container_name: portainer
restart: unless-stopped
ports:
- "9000:9000"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- portainer-data:/data
On Unraid, the same idea lives in the Docker template: repository/image, WebUI port, appdata config path, storage paths, and environment variables. The container can be replaced; the appdata and service data are the parts that need to survive.
How I use it day to day
- I use it to inspect container status, logs, volume mounts, and quick restart needs.
- I still use CLI for careful work, but Portainer makes state visible fast.
- I treat changes through Portainer with the same caution as shell commands.
Day to day, I try not to treat Docker like a mystery box. I check the service from the app UI, then the container status, then logs, then storage and networking. That order keeps me from randomly restarting things when the real issue is a bad path, a dead dependency, or an expired token.
What it connects to
- Docker socket
- Docker volumes
- Docker networks
- local browser admin
This matters because most container problems are not isolated. A media request app might be healthy but unable to reach Sonarr. Sonarr might be healthy but unable to reach a downloader. A web app might be healthy but failing because the database is gone. Mapping the connections makes troubleshooting faster.
How I would hook up notifications
- Portainer Business has richer notification features; for this setup I would use Uptime Kuma/n8n around Docker state.
- Send alerts when critical containers are unhealthy or down.
- Avoid noisy alerts for containers intentionally stopped.
My notification rule is simple: alert me when I need to act, not every time something makes noise. For public services, I care about uptime and response time. For automation services, I care about failed jobs and stuck queues. For sensitive services, I care about access, failed updates, and backup verification.
What I monitor
- Portainer availability
- Docker socket access
- admin login security
- container health
The minimum useful monitoring is container state plus one real application check. A container can be running while the app inside is broken, so I prefer checking the actual web endpoint, API health, or workflow behavior whenever possible.
What usually breaks first
- Docker socket unavailable
- Portainer data volume issue
- admin auth problem
- host Docker issue
When something breaks, I do not start by rebuilding the container. I first ask what changed: an image update, a config edit, a permission change, a moved folder, a full disk, a dead dependency, or an expired credential. Most Docker issues are boring once the dependencies are visible.
Backup and recovery notes
Back up the Portainer data volume if stacks, endpoints, or settings are managed there.
For recovery, I care about tested restores. A backup that has never been restored is only a guess. The practical goal is to know which folder, volume, database, or config file has to come back first so the service can be rebuilt without panic.
Security notes
Portainer has powerful Docker access. Protect it like root-level infrastructure.
I also avoid publishing secrets in these articles. Public notes can explain the architecture, the purpose, and the operating model without exposing passwords, tokens, private hostnames, tunnel IDs, or anything that gives someone a map to attack the setup.
Bottom line
Portainer earns a place in the lab when it solves a real problem and I can operate it without guessing. The point is not just having a container running. The point is knowing what it does, what depends on it, how I get notified, and how I recover it when something eventually breaks.
How I update it safely
I do not treat container updates like a blind button press. My safe update flow is: check the current container health, read what image is running, confirm backups or appdata are safe, update one service at a time when possible, then verify the web UI, logs, and any connected apps after the container comes back.
- Check whether the container is healthy before touching it.
- Back up appdata or confirm the backup path exists before risky upgrades.
- Update during a quiet window, especially for media and database-backed services.
- Verify the service after update with the UI, logs, and Uptime Kuma or a direct health check.
- If something breaks, roll back the image or restore appdata instead of guessing.