Podman Quadlet Examples for Immich, Nextcloud, and Vaultwarden
Start from curated multi-container Compose definitions for Immich, Nextcloud with MariaDB, Vaultwarden with Caddy, or Node with PostgreSQL and Redis. Adjust stack names, SELinux volume flags, and secret extraction in real time to inspect complete Quadlet unit sets.
systemd Deployment & Reload Commands
mkdir -p ~/.config/containers/systemd chmod 600 ~/.config/containers/systemd/immich.env systemctl --user daemon-reload && systemctl --user start immich-server.service immich-machine-learning.service redis.service database.service systemctl --user status immich-server.service immich-machine-learning.service redis.service database.service loginctl enable-linger $USER
Technical notes for Self-Hosted Templates
-
01
Multi-container stacks such as Immich combine server, machine-learning, Redis, and vector-enabled PostgreSQL units connected over a single <stack>.network unit.
-
02
Each service keeps its original Compose service name as NetworkAlias= or ContainerName= so internal connection strings like redis:6379 and database:5432 continue working unchanged.
-
03
Model caches and database directories use named .volume units while media upload folders stay mapped as host bind mounts.
-
04
Sensitive keys matching password, secret, token, or key patterns move into <stack>.env and connect via EnvironmentFile= across participating containers.
Syntax Mapping Reference
Compose Key -> Quadlet Directive Cheat Sheet
Quick lookup for how Compose YAML fields and docker or podman run flags translate into Podman systemd unit directives.
| Compose Key / CLI Flag | Unit Section | Quadlet Directive | Linux systemd Behavior |
|---|---|---|---|
| services.<app>.image | [Container] | Image=docker.io/library/... | Use a fully qualified registry host when AutoUpdate=registry is enabled. |
| ports: ["8080:80"] / -p | [Container] | PublishPort=8080:80 | Repeats once per published host port; supports bind IP and /udp protocol suffixes. |
| volumes: ["./data:/data"] / -v | [Container] + .volume | Volume=/srv/data:/data:Z | Named volumes map to <name>.volume units; bind mounts append :z or :Z on SELinux hosts. |
| environment / env_file / -e | [Container] | Environment= / EnvironmentFile= | Sensitive password, token, and key entries extract into <stack>.env with chmod 600. |
| depends_on | [Unit] | After=<dep>.service + Requires= | Starts PostgreSQL, MariaDB, and Redis units before dependent web or worker units. |
| networks (or stack default) | [Container] + .network | Network=<stack>.network | Creates an aardvark-dns bridge so peer containers resolve each other by service name. |
| restart: unless-stopped | [Service] + [Install] | Restart=always + WantedBy= | systemd restarts crashed containers and launches units on boot or user linger. |
| healthcheck.test / interval | [Container] | HealthCmd= / HealthInterval= | Translates CMD and CMD-SHELL probes along with retries, timeout, and start_period. |
| devices / cap_add / user | [Container] | AddDevice= / AddCapability= / User= | Passes /dev/dri GPU render nodes and scoped Linux capabilities without --privileged. |
| io.containers.autoupdate | [Container] | AutoUpdate=registry | Works with podman-auto-update.timer to pull newer image digests and roll services. |
Frequently asked questions
- Do Compose connection hostnames like postgres or redis still work in Quadlet?
- Yes. When all containers in the stack attach to the generated <stack>.network unit, Podman aardvark-dns registers container names and network aliases so services reach postgres:5432 or redis:6379 without code changes.
- How do I migrate existing Docker volumes when switching Immich or Nextcloud to Podman?
- Stop the Docker stack, copy bind-mounted host directories to your target path, or export named Docker volumes with tar and import them using podman volume import into the matching Quadlet .volume storage.
- Can I customize image tags or host ports after loading a built-in template?
- Yes. Edit the YAML directly in the left pane and every generated .container, .network, .volume, and .env file updates immediately.
- In what order does systemd start multi-container self-hosted templates?
- Network and volume units activate first, followed by database and cache units, and finally web or worker units that declare After= and Requires= from Compose depends_on.
Focused Workflows
Related Podman Quadlet Generators & Guides
Switch to another browser-local QuadletGen preset or read the systemd dry-run verification guide.
Docker Compose to Podman Quadlet Converter
Free browser-local Docker Compose to Quadlet converter. Compile compose.yaml into Podman systemd .container, .network, .volume, and .env ZIP units.
Podman Quadlet Generator for Declarative systemd Services
Interactive Podman Quadlet generator for declarative systemd services. Configure AutoUpdate=registry, health checks, rootless paths, and .env files.
Docker Run and Podman Run to Quadlet Converter
Paste any docker run or podman run command into this Podman run to Quadlet converter to generate clean .container systemd units with ports and mounts.
Rootless Podman Quadlet Volume and SELinux Label Generator
Configure rootless Podman Quadlet volume z and Z bind mount labels for Fedora, RHEL, Bluefin, and CoreOS without permission denied container errors.
Podlet Online Multi-Container Quadlet Network and ZIP Packager
Run a Podlet online workflow in your browser without Cargo or Rust. Package Compose stacks into linked .container, .network, .volume, and .env ZIPs.
QuadletGen Conversion Rules and systemd Dry-Run Verification
Review how QuadletGen synthesizes .container, .network, .volume, and .env units locally and how to verify syntax with podman/quadlet --dryrun.
How QuadletGen compares with containers/podlet CLI and Podman Desktop
Choose the right workflow for converting Compose stacks and container commands into Podman systemd units.
| Capability | QuadletGen (Web) | containers/podlet CLI | Podman Desktop |
|---|---|---|---|
| Host setup required | Zero installation in any browser | Rust Cargo build, distro package, or container image | Desktop GUI plus local Podman machine and extension |
| Multi-file stack preview | Live unit tabs, combined view, and one-click .zip bundle | Writes separate files to disk or stdout per CLI run | Inspects running local pods or containers one by one |
| Shared .network synthesis | Automatic <stack>.network generation on toggle | Converts declared Compose networks via CLI flags | Depends on existing local Podman network state |
| SELinux :z and :Z volume toggle | Instant switch across none, shared :z, and private :Z | Manual volume string editing in input YAML or flags | Manual edit after generating the unit file |
| Secret .env extraction | Extracts sensitive keys into <stack>.env with EnvironmentFile= | Preserves inline environment entries unless pre-split | Inline Environment= lines by default |
| Data privacy | 100% client-side JavaScript with zero server uploads | Local binary execution | Local desktop execution |