Rootless Podman, Quadlet and Docker migration
Author: DEWOLF.IT
Operate a rootless Podman service with Quadlet and verify images, identities, storage, labels and recovery.
This English edition covers the main steps. See the Dutch article for the full detail and examples.
Inventory the workload
Record the image, registry, published ports, persistent volumes, networks and environment required by the existing workload. Use an approved registry and pin an image by digest when it needs to be reproducible.
Understand the rootless boundary
Check the service user's subuid and subgid mapping, access to bind mounts, networking and port requirements. Verify data ownership and SELinux labels in the target environment. Treat changes to shared data, including recursive relabelling, as deliberate operations.
Manage the container as a user service
# ~/.config/containers/systemd/web.container
[Unit]
Description=Example rootless web container
[Container]
Image=docker.io/library/nginx:stable
PublishPort=127.0.0.1:8080:80
[Service]
Restart=on-failure
RestartSec=10s
TimeoutStartSec=300
[Install]
WantedBy=default.target
Check the Quadlet features for the installed Podman version. Reload and inspect the generated unit with the user's systemd manager. Verify machine restart behaviour and whether the use case requires a persistent user session.
Test migration and recovery
Validate the application with representative data, check that the service is reachable only where intended, test restart and restore, and document how to recover the service and its data.
See the Podman documentation.
