Operations
Day-to-day management of your containers: updates, backups, and maintenance.
Updating Containers
The default ghcr.io registry images are versioned using tags.
:latest- Builds daily from the upstream project's latest stable release.:pkg- Builds from FreeBSD quarterly packages.:pkg-latest- Builds from FreeBSD latest packages.
Podman CLI
- Pull new image:
- Stop and remove old container:
- Start new container:
Run your original
podman runcommand again. Since/configis a volume, your data persists.
Podman Compose
- Pull new images:
- Recreate containers:
This automatically stops the old container and creates a new one only if the image has changed.
Check that it really restarted
podman-compose up -d can exit 0 after failing to recreate a container. Check podman ps: the container's CREATED time should be just now.
Automated Updates
podman auto-update drives systemd units, which FreeBSD does not have. Schedule the pull and recreate instead, for example from /etc/crontab:
fjord updates a stack in one click and can roll the update back.
AppJail Director
appjail-director up leaves a running jail alone unless its spec changed. To move a service to a newer image, destroy its jail and bring the project up again; container: args:--pull in the service's options pulls the image as it rebuilds:
A sidecar in a bundle (a database, Redis) has no --pull: pull its image first with buildah pull --policy always <image>.
Backups
Backing up your data is critical. All daemonless containers store persistent data in the volume mounted to /config.
Backup Strategy
- Stop the container: Ensure database integrity (Radarr, Sonarr, etc. use SQLite).
- Archive the config directory:
- Restart the container:
ZFS Snapshots
If your data is on ZFS, you can use snapshots for instant backups without long downtime.
Maintenance
Pruning Images
Over time, old image layers can accumulate.
Checking Logs
If a container fails to start:
Everything the container prints, setup and app alike, is in podman logs.
On most images the app is the container's process: when it crashes, the
container exits and the restart policy brings it back. Multi-service appliances
restart the crashed service inside the running container instead. Either way the
crash is in the log:
Apps that write their own log files keep them under /config (for example
/path/to/config/radarr/logs/).