deuill/coreos-home-server
1
0
Fork 0
mirror of https://github.com/deuill/coreos-home-server.git synced 2024-09-21 21:50:46 +00:00
Code Issues Packages Projects Releases Wiki Activity
100951c118
coreos-home-server/config/common/systemd/container-volume-restore@.service

16 lines
647 B
SYSTEMD
Raw Normal View History

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=Restore from Backup for Container Volume %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
ConditionFileNotEmpty=%S/backups/coreos-home-server/%i/%i-latest.tar.gz
[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
ExecStart=/bin/podman run --replace --rm --name %p-%i --volume %i:/data:z --entrypoint /bin/bash \
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
--volume %S/backups/coreos-home-server/%i:/backups:z,ro \
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
docker.io/debian:stable-slim \
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
-c 'test -n "$(ls -A /data)" && echo "Volume %i is not empty, skipping." && exit 0; \
tar -xvpf "/backups/%i-latest.tar.gz" -C /data'
[Install]
WantedBy=multi-user.target
Reference in New Issue Copy Permalink