At home I run a small set of systems to manage storage and host a handful of applications — you could call it my homelab. Almost everything on it runs in containers. Recently I came across Portainer, a web UI for managing them, and it has earned a place in the setup.

Why containers in the first place

Containers suit a homelab really well:

  • They’re lightweight. No full VM per app — just the process and its dependencies, sharing the host kernel.
  • They spin up fast. When I change a config or try a new version, I can recreate the container in seconds.
  • They’re disposable. The app’s data lives on volumes, so I can throw a container away and rebuild it without losing anything.

Apps like Photoview and FileGator all run this way.

What Portainer gives me

Portainer Community Edition is itself just a container that talks to the Docker engine. Once it’s running, I get:

  • A dashboard showing every container, image, volume, and network at a glance — what’s running, what’s stopped, what’s unhealthy.
  • Live stats for CPU, memory, and network per container, which helps me spot the one that’s misbehaving.
  • Logs and a console in the browser, without SSH-ing in first.
  • Stacks — I can paste in a docker-compose.yml and deploy it from the UI.
  • Quick actions to start, stop, restart, or recreate a container.

The build

docker-compose.yml

services:
  portainer:
    image: portainer/portainer-ce:lts
    container_name: portainer
    restart: unless-stopped
    ports:
      - "9443:9443"
    volumes:
      # Lets Portainer manage the local Docker engine.
      - /var/run/docker.sock:/var/run/docker.sock
      # Portainer's own settings and users.
      - portainer_data:/data

volumes:
  portainer_data:
docker compose up -d

Then open https://<host>:9443 and create the admin user. Do it quickly — for security, Portainer only allows the initial admin setup for a few minutes after first start; if you miss it, just restart the container.

A word of caution: mounting docker.sock gives Portainer full control of the Docker host. That’s the point, but it also means the Portainer login is effectively root on that machine. Use a strong password and keep it off the public internet.

Honestly, I still prefer the terminal

As a Linux engineer, the terminal is home. docker ps, docker logs -f, docker compose up -d — that muscle memory isn’t going anywhere, and for anything scripted or repeatable, the CLI wins.

But Portainer isn’t trying to replace that. For me it’s:

  • A dashboard I can glance at to see the health of the whole lab.
  • A convenience for quick checks from a laptop or phone when I’m not at a terminal.

For now it helps, and that’s exactly what I want from a homelab tool: it earns its place without getting in the way.