Portainer CE

DevOps & Automation rootless 1 container
Open in Generator
portainer docker.io/portainer/portainer-ce:latest · 9443:9443, 9000:9000

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 portainer
passwd portainer

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

loginctl enable-linger portainer
↪

Switch to deployment user

su - portainer

Use su - with the dash — this creates a proper login shell as portainer. 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: portainer
  labels:
    app: portainer
spec:
  restartPolicy: Always
  containers:
  - name: portainer
    image: docker.io/portainer/portainer-ce:latest
    imagePullPolicy: Always
    ports:
    - containerPort: 9443
      hostPort: 9443
    - containerPort: 9000
      hostPort: 9000
    volumeMounts:
    - name: vol-0
      mountPath: /data
    - name: vol-1
      mountPath: /var/run/docker.sock
  volumes:
  - name: vol-0
    persistentVolumeClaim:
      claimName: portainer-data
  - name: vol-1
    hostPath:
      path: /run/user/1000/podman/podman.sock
      type: FileOrCreate
1

Save the YAML file

mkdir -p ~/.config/containers/
nano ~/.config/containers/portainer.yaml
2

Test the pod (without autostart)

podman kube play ~/.config/containers/portainer.yaml

# Check status:
podman pod ps && podman ps

# Stop:
podman kube down ~/.config/containers/portainer.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/portainer.yaml).service

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

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

3

Create Quadlet .kube file

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

[Kube]
Yaml=%h/.config/containers/portainer.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/portainer.kube
4

Start systemd service

systemctl --user daemon-reload
systemctl --user start portainer.service
5

Status & Logs

systemctl --user status portainer.service
journalctl --user -u portainer.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 portainer-portainer
podman exec -it portainer-portainer /bin/sh

Restart

systemctl --user restart portainer.service

Update an image by hand

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

podman pull <image>:<tag>
systemctl --user restart portainer.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 portainer.service
rm ~/.config/containers/systemd/portainer.kube
systemctl --user daemon-reload

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

systemctl --user restart podman-kube@$(systemd-escape ~/.config/containers/portainer.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/portainer.yaml).service

Delete the data — permanent, only after stop & remove

podman volume rm portainer-data
podman unshare rm -rf /run/user/1000/podman/podman.sock

Files created by containers belong to root in the user namespace — podman unshare is required to delete them.

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

portainer.pod 
[Unit]
Description=portainer pod

[Pod]
PodName=portainer
PublishPort=9443:9443
PublishPort=9000:9000
portainer-portainer.container 
[Unit]
Description=portainer-portainer container

[Container]
Image=docker.io/portainer/portainer-ce:latest
Pod=portainer.pod
ContainerName=portainer-portainer
Pull=always
Volume=portainer-data:/data:Z
Volume=/run/user/1000/podman/podman.sock:/var/run/docker.sock

[Service]
Restart=always

[Install]
WantedBy=default.target

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

mkdir -p ~/.config/containers/systemd/
nano ~/.config/containers/systemd/portainer.pod
nano ~/.config/containers/systemd/portainer-portainer.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 portainer-pod.service
3

Status & Logs

systemctl --user status portainer-pod.service
journalctl --user -u portainer-portainer.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 portainer-portainer
podman exec -it portainer-portainer /bin/sh

Restart

systemctl --user restart portainer-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 portainer-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 portainer-pod.service
rm ~/.config/containers/systemd/portainer.pod
rm ~/.config/containers/systemd/portainer-portainer.container
systemctl --user daemon-reload

Delete the data — permanent, only after stop & remove

podman volume rm portainer-data
podman unshare rm -rf /run/user/1000/podman/podman.sock

Files created by containers belong to root in the user namespace — podman unshare is required to delete them.

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 - portainer.

apt install -y podman-compose
2

Save the compose file

docker-compose.yml 
services:
  portainer:
    image: docker.io/portainer/portainer-ce:latest
    pull_policy: always
    restart: always
    ports:
    - 9443:9443
    - 9000:9000
    volumes:
    - portainer-data:/data:Z
    - /run/user/1000/podman/podman.sock:/var/run/docker.sock
volumes:
  portainer-data: null

mkdir -p ~/portainer
nano ~/portainer/docker-compose.yml
3

Start, status & logs

cd ~/portainer
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 ~/portainer
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 portainer_portainer_1
podman exec -it portainer_portainer_1 /bin/sh

Restart

cd ~/portainer
podman-compose restart

Stop & remove

cd ~/portainer
podman-compose down

Delete the data — permanent, only after stop & remove

podman volume rm portainer_portainer-data
podman unshare rm -rf /run/user/1000/podman/podman.sock

Files created by containers belong to root in the user namespace — podman unshare is required to delete them.

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

1

Save the script

portainer.sh 
#!/bin/bash
set -e

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

# ── Create pod ─────────────────────────────────────────────────────
podman pod create \
  --name portainer \
  -p 9443:9443 \
  -p 9000:9000

# ── Container: portainer-portainer ─────────────────────────────────────────────
podman create \
  --pod portainer \
  --name portainer-portainer \
  --restart always \
  --pull always \
  -v portainer-data:/data:Z \
  -v /run/user/1000/podman/podman.sock:/var/run/docker.sock \
  docker.io/portainer/portainer-ce:latest

# ── Start pod ──────────────────────────────────────────────────────
podman pod start portainer

# ── Stop & clean up ───────────────────────────────────────────────
# podman pod stop portainer
# podman pod rm portainer
nano portainer.sh
2

Run it, status & logs

bash portainer.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 portainer
bash portainer.sh
Day-to-day logs, restart, update, remove (click to open)

Logs & shell into a container

podman logs -f portainer-portainer
podman exec -it portainer-portainer /bin/sh

Restart

podman pod stop portainer
podman pod start portainer

Stop & remove

podman pod rm -f portainer

Delete the data — permanent, only after stop & remove

podman volume rm portainer-data
podman unshare rm -rf /run/user/1000/podman/podman.sock

Files created by containers belong to root in the user namespace — podman unshare is required to delete them.

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