Uptime Kuma

Monitoring rootless 1 container
Open in Generator
uptime-kuma docker.io/louislam/uptime-kuma:latest · 3001:3001

Deployment rootless

1. Prepare the host

Operating System:
!

Prerequisites once as root

Install Podman (needs podman 4.3 or newer; Ubuntu 22.04 ships 3.4 and is too old, use 24.04)

apt update && apt install -y podman

Create user (if not existing)

useradd -m -s /bin/bash uptime-kuma
passwd uptime-kuma

Enable linger (services keep running after logout and start after reboot)

loginctl enable-linger uptime-kuma
↪

Switch to deployment user

su - uptime-kuma

Use su - with the dash — this creates a proper login shell as uptime-kuma. Without the dash, root environment variables carry over and rootless Podman will not work correctly.

!

Fix environment for rootless systemd (new users only — skip if already set)

Required once so systemctl --user works in non-login sessions.

cat << 'EOF' >> ~/.bashrc

# Fix for systemd user services (rootless Podman/systemctl)
export XDG_RUNTIME_DIR=/run/user/$(id -u)
export DBUS_SESSION_BUS_ADDRESS=unix:path=$XDG_RUNTIME_DIR/bus
EOF
source ~/.bashrc

2. Choose a format and deploy

The same pod in four forms. Pick one and follow only its steps.

Each tab says which podman it needs. Check yours with podman --version: Debian 12 ships 4.3, Ubuntu 24.04 4.9, Debian 13 5.4, Fedora 5.8, Arch 6.x.

Kubernetes YAML for podman kube play, started by systemd through a Quadlet .kube unit (podman 4.4+; older podman like Debian 12 uses podman-kube@, see the version check below).

Kubernetes YAML 

apiVersion: v1
kind: Pod
metadata:
  name: uptime-kuma
  labels:
    app: uptime-kuma
spec:
  restartPolicy: Always
  containers:
  - name: uptime-kuma
    image: docker.io/louislam/uptime-kuma:latest
    imagePullPolicy: Always
    ports:
    - containerPort: 3001
      hostPort: 3001
    volumeMounts:
    - name: vol-0
      mountPath: /app/data
  volumes:
  - name: vol-0
    persistentVolumeClaim:
      claimName: uptime-kuma-data
1

Save the YAML file

mkdir -p ~/.config/containers/
nano ~/.config/containers/uptime-kuma.yaml
2

Test the pod (without autostart)

podman kube play ~/.config/containers/uptime-kuma.yaml

# Check status:
podman pod ps && podman ps

# Stop:
podman kube down ~/.config/containers/uptime-kuma.yaml

Check your podman version

podman --version

4.4 or newer: continue with step 3 below.

Older, e.g. 4.3 on Debian 12? There is no Quadlet yet: use podman's own podman-kube@ service instead of steps 3–5 
systemctl --user enable --now podman-kube@$(systemd-escape ~/.config/containers/uptime-kuma.yaml).service

# Status & logs:
systemctl --user status podman-kube@$(systemd-escape ~/.config/containers/uptime-kuma.yaml).service
journalctl --user -u podman-kube@$(systemd-escape ~/.config/containers/uptime-kuma.yaml).service -f

The day-to-day commands below have a block for this service.

3

Create Quadlet .kube file

uptime-kuma.kube 
[Unit]
Description=uptime-kuma pod
After=network-online.target
Wants=network-online.target

[Kube]
Yaml=%h/.config/containers/uptime-kuma.yaml

[Service]
Restart=always

[Install]
WantedBy=default.target

%h is a systemd home-directory specifier — do not replace it with ~/.

Save to ~/.config/containers/systemd/:

mkdir -p ~/.config/containers/systemd/
nano ~/.config/containers/systemd/uptime-kuma.kube
4

Start systemd service

systemctl --user daemon-reload
systemctl --user start uptime-kuma.service
5

Status & Logs

systemctl --user status uptime-kuma.service
journalctl --user -u uptime-kuma.service -f
podman pod ps
podman ps
6

Enable automatic image updates optional

Requires AutoUpdate=registry in the .kube file. Podman then checks for new images and restarts the pod automatically:

systemctl --user enable --now podman.socket
systemctl --user daemon-reload
systemctl --user enable --now podman-auto-update.timer

# Check status:
systemctl --user status podman-auto-update.timer

# Trigger manually:
podman auto-update
Day-to-day logs, restart, update, remove (click to open)

Logs & shell into a container

podman logs -f uptime-kuma-uptime-kuma
podman exec -it uptime-kuma-uptime-kuma /bin/sh

Restart

systemctl --user restart uptime-kuma.service

Update an image by hand

Pull the new version, the restart recreates the containers from it:

podman pull <image>:<tag>
systemctl --user restart uptime-kuma.service

Stop & remove

Stop through systemd, otherwise Restart=always brings the pod back. To remove it for good, delete the unit files and reload:

systemctl --user stop uptime-kuma.service
rm ~/.config/containers/systemd/uptime-kuma.kube
systemctl --user daemon-reload

podman older than 4.4 (podman-kube@ from step 3)

systemctl --user restart podman-kube@$(systemd-escape ~/.config/containers/uptime-kuma.yaml).service

# Update an image: pull, then restart as above
podman pull <image>:<tag>

# Stop and remove from autostart:
systemctl --user disable --now podman-kube@$(systemd-escape ~/.config/containers/uptime-kuma.yaml).service

Delete the data — permanent, only after stop & remove

podman volume rm uptime-kuma-data

Native systemd units without the Kubernetes YAML: one .pod plus one .container per container. Each container becomes its own systemd service (restart, logs and ordering per container). Needs podman 5.0 or newer — Debian 12 ships 4.3, use the Kube YAML tab there.

1

Save the unit files

uptime-kuma.pod 
[Unit]
Description=uptime-kuma pod

[Pod]
PodName=uptime-kuma
PublishPort=3001:3001
uptime-kuma-uptime-kuma.container 
[Unit]
Description=uptime-kuma-uptime-kuma container

[Container]
Image=docker.io/louislam/uptime-kuma:latest
Pod=uptime-kuma.pod
ContainerName=uptime-kuma-uptime-kuma
Pull=always
Volume=uptime-kuma-data:/app/data:Z

[Service]
Restart=always

[Install]
WantedBy=default.target

Save all of them to ~/.config/containers/systemd/:

mkdir -p ~/.config/containers/systemd/
nano ~/.config/containers/systemd/uptime-kuma.pod
nano ~/.config/containers/systemd/uptime-kuma-uptime-kuma.container
2

Start the pod

The pod service pulls in every container service. Autostart at boot comes from the [Install] section of the units, no enable needed.

systemctl --user daemon-reload
systemctl --user start uptime-kuma-pod.service
3

Status & Logs

systemctl --user status uptime-kuma-pod.service
journalctl --user -u uptime-kuma-uptime-kuma.service -f
podman pod ps && podman ps
Day-to-day logs, restart, update, remove (click to open)

Logs & shell into a container

podman logs -f uptime-kuma-uptime-kuma
podman exec -it uptime-kuma-uptime-kuma /bin/sh

Restart

systemctl --user restart uptime-kuma-pod.service

Update an image by hand

Pull the new version, the restart recreates the containers from it:

podman pull <image>:<tag>
systemctl --user restart uptime-kuma-pod.service

Stop & remove

Stop through systemd, otherwise Restart=always brings the pod back. To remove it for good, delete the unit files and reload:

systemctl --user stop uptime-kuma-pod.service
rm ~/.config/containers/systemd/uptime-kuma.pod
rm ~/.config/containers/systemd/uptime-kuma-uptime-kuma.container
systemctl --user daemon-reload

Delete the data — permanent, only after stop & remove

podman volume rm uptime-kuma-data

A docker-compose.yml for podman-compose. Handy if you already work with Compose; there are no per-container systemd services.

1

Install podman-compose as root

Run this as root, e.g. together with the prerequisites before su - uptime-kuma.

apt install -y podman-compose
2

Save the compose file

docker-compose.yml 
services:
  uptime-kuma:
    image: docker.io/louislam/uptime-kuma:latest
    pull_policy: always
    restart: always
    ports:
    - 3001:3001
    volumes:
    - uptime-kuma-data:/app/data:Z
volumes:
  uptime-kuma-data: null

mkdir -p ~/uptime-kuma
nano ~/uptime-kuma/docker-compose.yml
3

Start, status & logs

cd ~/uptime-kuma
podman-compose up -d
podman-compose ps
podman-compose logs -f

# Stop:
podman-compose down
4

Start after reboot

podman-restart.service starts every container with restart: always at boot:

systemctl --user enable podman-restart.service
5

Update images

cd ~/uptime-kuma
podman-compose pull
podman-compose up -d
Day-to-day logs, restart, update, remove (click to open)

Logs & shell into a container

podman logs -f uptime-kuma_uptime-kuma_1
podman exec -it uptime-kuma_uptime-kuma_1 /bin/sh

Restart

cd ~/uptime-kuma
podman-compose restart

Stop & remove

cd ~/uptime-kuma
podman-compose down

Delete the data — permanent, only after stop & remove

podman volume rm uptime-kuma_uptime-kuma-data

Plain podman pod create / podman create commands. Good for a quick test or to see what happens under the hood.

1

Save the script

uptime-kuma.sh 
#!/bin/bash
set -e

# ── Create named volumes ───────────────────────────────────────────
# Named volumes are created automatically — no UID/GID permission adjustment needed.
podman volume exists uptime-kuma-data || podman volume create uptime-kuma-data

# ── Create pod ─────────────────────────────────────────────────────
podman pod create \
  --name uptime-kuma \
  -p 3001:3001

# ── Container: uptime-kuma-uptime-kuma ─────────────────────────────────────────────
podman create \
  --pod uptime-kuma \
  --name uptime-kuma-uptime-kuma \
  --restart always \
  --pull always \
  -v uptime-kuma-data:/app/data:Z \
  docker.io/louislam/uptime-kuma:latest

# ── Start pod ──────────────────────────────────────────────────────
podman pod start uptime-kuma

# ── Stop & clean up ───────────────────────────────────────────────
# podman pod stop uptime-kuma
# podman pod rm uptime-kuma
nano uptime-kuma.sh
2

Run it, status & logs

bash uptime-kuma.sh
podman pod ps && podman ps
podman logs -f <container-name>
3

Start after reboot

podman-restart.service starts every container with --restart always at boot:

systemctl --user enable podman-restart.service
4

Remove or rebuild

The script creates the pod once. To apply changes or new images, remove the pod and run the script again (named volumes stay):

podman pod rm -f uptime-kuma
bash uptime-kuma.sh
Day-to-day logs, restart, update, remove (click to open)

Logs & shell into a container

podman logs -f uptime-kuma-uptime-kuma
podman exec -it uptime-kuma-uptime-kuma /bin/sh

Restart

podman pod stop uptime-kuma
podman pod start uptime-kuma

Stop & remove

podman pod rm -f uptime-kuma

Delete the data — permanent, only after stop & remove

podman volume rm uptime-kuma-data
Useful Tips

Ports < 1024 (e.g. 80, 443)

Rootless cannot open privileged ports. Solution:

sysctl net.ipv4.ip_unprivileged_port_start=80

Make persistent in /etc/sysctl.d/99-podman.conf.

Containers communicate via localhost

All containers in the pod share the same network namespace. Always use localhost, not container names.

# Correct (e.g. app → db):
localhost:5432

# Wrong (doesn't work in a pod):
db-container:5432

List open ports

Which ports are the running containers publishing? See the PORTS column:

podman ps

Custom DNS for the pod

Set a custom DNS server (e.g. local Pi-hole) in the generator under DNS server. Every format picks it up.

Set volume ownership

Fix permission errors by adjusting UID/GID in the user namespace:

podman unshare chown 1000:1000 /path/to/volume

SELinux volume labels

On SELinux systems (RHEL, Fedora) set the volume suffix:

/host/path:/container/path:Z   # private
/host/path:/container/path:z   # shared

List all volumes

podman volume ls
podman volume inspect <volume-name>

Volume backup

Back up data from a named volume:

podman run --rm \
  -v <volume-name>:/data:ro \
  -v $(pwd):/backup \
  busybox tar czf /backup/backup.tar.gz /data

Cleanup

Remove unused images, containers and volumes:

podman system prune -f        # containers + images
podman image prune -f         # untagged images only
podman volume prune -f        # unused volumes

Check for outdated images

List local images; auto-update only covers units with AutoUpdate= (Kube and Quadlet tabs):

podman images
podman auto-update --dry-run

All containers, including stopped ones

podman pod ps
podman ps -a

Resource usage

podman stats --no-stream
Customize this stack
Change ports, volumes, environment variables and more in the generator.
Open in Generator