Reference Deployment with Podman Quadlet
Overview¶
This document shows how to run the reference SSL deployment (PostgreSQL, the Sicura Console, and an Nginx reverse proxy for SSL termination) as systemd services using Podman Quadlet. Quadlet turns short unit files into systemd services, so the whole stack starts on boot, restarts on failure, and is managed with systemctl like any other service.
Prerequisites¶
- A Linux system with:
- Podman 4.4 or later (Quadlet is part of Podman from that version)
- TCP ports 443 and (optionally) 80 (for redirection to port 443) allowed
- A Sicura license key, saved as
/etc/sicura/console/license.key - A Sicura Console configuration file, saved as
/etc/sicura/console/sicura-console.yaml - SSL certificates in
/etc/sicura/nginx/certs/(fullchain.pemandprivkey.pem) - The Nginx configuration template in
/etc/sicura/nginx/templates/default.conf.template
Package installation, firewall configuration, and self-signed certificate generation are the same as in the reference SSL deployment; follow its Prerequisites first.
The Nginx template is the one from Create an Nginx Configuration Template, with one change: there is no pod in this deployment, so the proxy target is the Console container's name. Replace the line proxy_pass http://sicura:80; with proxy_pass http://sicura-console:80;.
Note: The commands below run the stack as root (rootful Podman). For a rootless deployment, put the Quadlet files in ~/.config/containers/systemd/ and the target in ~/.config/systemd/user/, use systemctl --user and podman secret create as that user, enable lingering with loginctl enable-linger, and allow the user to bind ports 80 and 443 (for example sysctl net.ipv4.ip_unprivileged_port_start=80).
Create the Database Password Secret¶
Secrets are not part of Quadlet; create the database password once, before starting the stack:
Quadlet Unit Files¶
Create the following files in /etc/containers/systemd/. Quadlet reads .network, .volume, and .container files from that directory and generates one systemd service from each.
sicura.network¶
Containers on this network reach each other by container name, which is how the Console finds sicura-db and Nginx finds sicura-console.
sicura-dbdata.volume¶
sicura-db.container¶
[Unit]
Description=Sicura PostgreSQL Database
PartOf=sicura.target
[Container]
ContainerName=sicura-db
Image=docker.io/library/postgres:17
Network=sicura.network
Volume=sicura-dbdata.volume:/var/lib/postgresql/data:Z
Secret=sicura-db-password,type=env,target=POSTGRES_PASSWORD
HealthCmd=pg_isready -U postgres
HealthInterval=5s
HealthTimeout=5s
HealthRetries=5
[Service]
Restart=on-failure
RestartSec=5s
[Install]
WantedBy=sicura.target
sicura-console.container¶
[Unit]
Description=Sicura Console
Requires=sicura-db.service
After=sicura-db.service
PartOf=sicura.target
[Container]
ContainerName=sicura-console
Image=registry.customers.sicura.us/products/sicura-console:2026.9.0
Network=sicura.network
Volume=/etc/sicura/console:/etc/sicura/config:ro,Z
Environment=DB_HOST=sicura-db
Environment=DB_PORT=5432
Environment=DB_USER=postgres
Environment=DB_DATABASE=postgres
Environment=DB_SSLMODE=disable
Environment=SICURA_LICENSE_KEY_FILE=/etc/sicura/config/license.key
Environment=SICURA_CONFIG_FILE=/etc/sicura/config/sicura-console.yaml
Secret=sicura-db-password,type=env,target=DB_PASSWORD
[Service]
Restart=on-failure
RestartSec=5s
[Install]
WantedBy=sicura.target
The Secret=...,type=env,target=... lines inject the secret's contents as an environment variable. Setting Environment=DB_PASSWORD=/run/secrets/... instead would make the literal path the password. The full list of Console environment variables is in Console Environment Variables.
sicura-nginx.container¶
[Unit]
Description=Sicura Nginx Reverse Proxy
Requires=sicura-console.service
After=sicura-console.service
PartOf=sicura.target
[Container]
ContainerName=sicura-nginx
Image=docker.io/library/nginx:latest
Network=sicura.network
Volume=/etc/sicura/nginx/templates:/etc/nginx/templates:ro,Z
Volume=/etc/sicura/nginx/certs:/etc/nginx/certs:ro,Z
Environment=SERVER_NAME=<console-fqdn>
Environment=SSL_CERT=/etc/nginx/certs/fullchain.pem
Environment=SSL_KEY=/etc/nginx/certs/privkey.pem
PublishPort=80:80
PublishPort=443:443
[Service]
Restart=on-failure
RestartSec=5s
[Install]
WantedBy=sicura.target
Replace <console-fqdn> with the fully qualified hostname that matches your certificate.
The sicura.target Unit¶
A systemd target groups the three services so the stack starts, stops, and enables as one unit. It is a plain systemd unit, not a Quadlet file, so it goes in /etc/systemd/system/sicura.target (Quadlet ignores .target files placed in its own directory):
Deployment Steps¶
Check the Quadlet Files¶
Run the Quadlet generator in dry-run mode. It prints the systemd services it would generate and reports any syntax or configuration error:
Generate the Services¶
The listing should show sicura-network.service, sicura-dbdata-volume.service, sicura-db.service, sicura-console.service, sicura-nginx.service, and sicura.target.
Start the Stack¶
Verify Deployment¶
Check the services and the container logs:
The Sicura Console should be accessible over HTTPS at https://<console-fqdn>/.
Enable the Stack at Boot¶
Reboot the system and confirm the Console comes back without intervention.
Managing the Stack¶
- Stop everything —
systemctl stop sicura.target - Restart one service —
systemctl restart sicura-console.service - Upgrade the Console — change the
Image=tag insicura-console.container, then runsystemctl daemon-reloadandsystemctl restart sicura-console.service. See Upgrades for release notes and upgrade caveats.