coreos-home-server/config/common/systemd/container-volume@.service

[Unit]
Description=Container Volume for %I
Wants=container-volume-restore@%i.service container-volume-backup@%i.timer
After=container-volume-restore@%i.service

[Service]
Type=oneshot
SyslogIdentifier=%N
ExecStart=/bin/sh -c 'podman volume exists %i || podman volume create %i'

[Install]
WantedBy=multi-user.target
Implement basic volume backup and restore mechanism This commit implements three new services, specifically: - The `container-volume` service, which applies to a specific volume name and ensures this exists. This is mainly useful as a dependency to other services, as Podman will create named volumes itself if needed. - The `container-volume-backup` service, which creates a `tar.gz` snapshot of the given volume's contents in `/var/lib/backups`. - The `container-volume-restore` service, which populates an empty volume from a pre-existing file in `/var/lib/backups`, presumably created by `container-volume-backup`. These are then be used to automatically create volume snapshots every 12 hours, rolling over every 7 days. 2021-08-14 21:31:02 +00:00			`[Unit]`
Fix title-casing for service descriptions 2021-08-28 11:51:11 +00:00			`Description=Container Volume for %I`
Implement basic volume backup and restore mechanism This commit implements three new services, specifically: - The `container-volume` service, which applies to a specific volume name and ensures this exists. This is mainly useful as a dependency to other services, as Podman will create named volumes itself if needed. - The `container-volume-backup` service, which creates a `tar.gz` snapshot of the given volume's contents in `/var/lib/backups`. - The `container-volume-restore` service, which populates an empty volume from a pre-existing file in `/var/lib/backups`, presumably created by `container-volume-backup`. These are then be used to automatically create volume snapshots every 12 hours, rolling over every 7 days. 2021-08-14 21:31:02 +00:00			`Wants=container-volume-restore@%i.service container-volume-backup@%i.timer`
			`After=container-volume-restore@%i.service`

			`[Service]`
			`Type=oneshot`
Set generic Podman defaults and per-service log IDs Defaults for Podman that were previous applied as command-line arguments to all `podman run` or `podman create` invocations are now specified in a dedicated configuration file. Services are also better identified against their name rather than the generic `podman` ID derived from the `ExecStart` invocations. 2021-08-28 18:16:29 +00:00			`SyslogIdentifier=%N`
Implement basic volume backup and restore mechanism This commit implements three new services, specifically: - The `container-volume` service, which applies to a specific volume name and ensures this exists. This is mainly useful as a dependency to other services, as Podman will create named volumes itself if needed. - The `container-volume-backup` service, which creates a `tar.gz` snapshot of the given volume's contents in `/var/lib/backups`. - The `container-volume-restore` service, which populates an empty volume from a pre-existing file in `/var/lib/backups`, presumably created by `container-volume-backup`. These are then be used to automatically create volume snapshots every 12 hours, rolling over every 7 days. 2021-08-14 21:31:02 +00:00			`ExecStart=/bin/sh -c 'podman volume exists %i \|\| podman volume create %i'`

			`[Install]`
			`WantedBy=multi-user.target`