WordPress

Web & Communication rootless 2 containers
Open in Generator
wordpress docker.io/wordpress:latest · 8080:80
mariadb docker.io/mariadb:11

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

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

loginctl enable-linger wordpress
↪

Switch to deployment user

su - wordpress

Use su - with the dash — this creates a proper login shell as wordpress. 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: wordpress
  labels:
    app: wordpress
spec:
  restartPolicy: Always
  containers:
  - name: wordpress
    image: docker.io/wordpress:latest
    imagePullPolicy: Always
    ports:
    - containerPort: 80
      hostPort: 8080
    env:
    - name: WORDPRESS_DB_HOST
      value: 127.0.0.1:3306
    - name: WORDPRESS_DB_USER
      value: wordpress
    - name: WORDPRESS_DB_PASSWORD
      value: uQ37mh_LAceZ6Df3OcjGBA
    - name: WORDPRESS_DB_NAME
      value: wordpress
    volumeMounts:
    - name: vol-0
      mountPath: /var/www/html
  - name: mariadb
    image: docker.io/mariadb:11
    env:
    - name: MARIADB_ROOT_PASSWORD
      value: a-Pfh8qIyu3A2Qqp5mYCmQ
    - name: MARIADB_USER
      value: wordpress
    - name: MARIADB_PASSWORD
      value: uQ37mh_LAceZ6Df3OcjGBA
    - name: MARIADB_DATABASE
      value: wordpress
    volumeMounts:
    - name: vol-1
      mountPath: /var/lib/mysql
    securityContext:
      runAsUser: 999
      runAsGroup: 999
  volumes:
  - name: vol-0
    persistentVolumeClaim:
      claimName: wordpress-html
  - name: vol-1
    persistentVolumeClaim:
      claimName: wordpress-db
1

Save the YAML file

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

Test the pod (without autostart)

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

# Check status:
podman pod ps && podman ps

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

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

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

3

Create Quadlet .kube file

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

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

Start systemd service

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

Status & Logs

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

Restart

systemctl --user restart wordpress.service

Update an image by hand

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

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

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

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

Delete the data — permanent, only after stop & remove

podman volume rm wordpress-html
podman volume rm wordpress-db

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

wordpress.pod 
[Unit]
Description=wordpress pod

[Pod]
PodName=wordpress
PublishPort=8080:80
wordpress-wordpress.container 
[Unit]
Description=wordpress-wordpress container

[Container]
Image=docker.io/wordpress:latest
Pod=wordpress.pod
ContainerName=wordpress-wordpress
Pull=always
Environment=WORDPRESS_DB_HOST=127.0.0.1:3306
Environment=WORDPRESS_DB_USER=wordpress
Environment=WORDPRESS_DB_PASSWORD=uQ37mh_LAceZ6Df3OcjGBA
Environment=WORDPRESS_DB_NAME=wordpress
Volume=wordpress-html:/var/www/html:Z

[Service]
Restart=always

[Install]
WantedBy=default.target
wordpress-mariadb.container 
[Unit]
Description=wordpress-mariadb container

[Container]
Image=docker.io/mariadb:11
Pod=wordpress.pod
ContainerName=wordpress-mariadb
Environment=MARIADB_ROOT_PASSWORD=a-Pfh8qIyu3A2Qqp5mYCmQ
Environment=MARIADB_USER=wordpress
Environment=MARIADB_PASSWORD=uQ37mh_LAceZ6Df3OcjGBA
Environment=MARIADB_DATABASE=wordpress
Volume=wordpress-db:/var/lib/mysql:Z
User=999
Group=999

[Service]
Restart=always

[Install]
WantedBy=default.target

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

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

Status & Logs

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

Restart

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

Delete the data — permanent, only after stop & remove

podman volume rm wordpress-html
podman volume rm wordpress-db

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

apt install -y podman-compose
2

Save the compose file

docker-compose.yml 
services:
  wordpress:
    image: docker.io/wordpress:latest
    pull_policy: always
    restart: always
    environment:
    - WORDPRESS_DB_HOST=127.0.0.1:3306
    - WORDPRESS_DB_USER=wordpress
    - WORDPRESS_DB_PASSWORD=uQ37mh_LAceZ6Df3OcjGBA
    - WORDPRESS_DB_NAME=wordpress
    depends_on:
      mariadb:
        condition: service_started
    volumes:
    - wordpress-html:/var/www/html:Z
    network_mode: service:mariadb
  mariadb:
    image: docker.io/mariadb:11
    restart: always
    environment:
    - MARIADB_ROOT_PASSWORD=a-Pfh8qIyu3A2Qqp5mYCmQ
    - MARIADB_USER=wordpress
    - MARIADB_PASSWORD=uQ37mh_LAceZ6Df3OcjGBA
    - MARIADB_DATABASE=wordpress
    user: 999:999
    volumes:
    - wordpress-db:/var/lib/mysql:Z
    ports:
    - 8080:80
volumes:
  wordpress-html: null
  wordpress-db: null

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

Start, status & logs

cd ~/wordpress
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 ~/wordpress
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 wordpress_wordpress_1
podman logs -f wordpress_mariadb_1
podman exec -it wordpress_wordpress_1 /bin/sh

Restart

cd ~/wordpress
podman-compose restart

Stop & remove

cd ~/wordpress
podman-compose down

Delete the data — permanent, only after stop & remove

podman volume rm wordpress_wordpress-html
podman volume rm wordpress_wordpress-db

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

1

Save the script

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

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

# ── Create pod ─────────────────────────────────────────────────────
podman pod create \
  --name wordpress \
  -p 8080:80

# ── Container: wordpress-wordpress ─────────────────────────────────────────────
podman create \
  --pod wordpress \
  --name wordpress-wordpress \
  --restart always \
  --pull always \
  -e WORDPRESS_DB_HOST='127.0.0.1:3306' \
  -e WORDPRESS_DB_USER='wordpress' \
  -e WORDPRESS_DB_PASSWORD='uQ37mh_LAceZ6Df3OcjGBA' \
  -e WORDPRESS_DB_NAME='wordpress' \
  -v wordpress-html:/var/www/html:Z \
  docker.io/wordpress:latest

# ── Container: wordpress-mariadb ─────────────────────────────────────────────
podman create \
  --pod wordpress \
  --name wordpress-mariadb \
  --restart always \
  -e MARIADB_ROOT_PASSWORD='a-Pfh8qIyu3A2Qqp5mYCmQ' \
  -e MARIADB_USER='wordpress' \
  -e MARIADB_PASSWORD='uQ37mh_LAceZ6Df3OcjGBA' \
  -e MARIADB_DATABASE='wordpress' \
  -v wordpress-db:/var/lib/mysql:Z \
  --user 999:999 \
  docker.io/mariadb:11

# ── Start pod ──────────────────────────────────────────────────────
podman pod start wordpress

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

Run it, status & logs

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

Logs & shell into a container

podman logs -f wordpress-wordpress
podman logs -f wordpress-mariadb
podman exec -it wordpress-wordpress /bin/sh

Restart

podman pod stop wordpress
podman pod start wordpress

Stop & remove

podman pod rm -f wordpress

Delete the data — permanent, only after stop & remove

podman volume rm wordpress-html
podman volume rm wordpress-db
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