mirror of
https://github.com/lobaro/restic-backup-docker.git
synced 2026-11-13 15:45:22 +00:00
Adds structure, compat and feature-gated container test suites (test/run.sh), runs them in CI, and gates image publishing on a green test run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.0 KiB
2.0 KiB
Changelog
Unreleased
Added
- Test suites in
test/(compat, features, structure) that run the image as a real container, plus aTestGitHub Actions workflow running them on every pull request .gitattributespinning shell scripts, the Dockerfile and YAML files to LF line endings. With a Windows checkout (core.autocrlf=true) the scripts were checked out with CRLF, which made the built image fail to start withexec /entry.sh: no such file or directory
Removed
config-broken.ymlanddocker-compose.test.broken.yml, replaced bytest/structure.ymland the test workflow
v1.4.2
Removed
- Execute a repository check after prune was passed as a parameter in the forget call - use RESTIC_CHECK_CRON Var instead
v1.4.1
Changed
- Execute a repository check after prune was passed as a parameter in the forget call
v1.4.0
Added
- Option to set the target folder backup
- Multi-platform image build
v1.3.2 (restic 0.16.0)
Changed
- Base image directly on official restic image
- Semver aligned version naming including restic version
- Updated to restic 0.16.0
Added
- rclone to docker image
- Implemented a simple mail notification after backups using mailx
- MAILX_ARGS environment variable
v1.3.1-0.9.6
Changed
- Update to Restic v0.9.5
- Reduced the number of layers in the Docker image
Fixed
- Check if a repo already exists works now for all repository types
Added
- shh added to container
- fuse added to container
- support to send mails using external SMTP server after backups
v1.2-0.9.4
Added
- AWS Support
v1.1
Fixed
--prunemust be passed toRESTIC_FORGET_ARGSto execute prune after forget.
Changed
- Switch to base Docker container to
golang:1.7-alpineto support latest restic build.
v1.0
Initial release.
The container has proper logs now and was running for over a month in production. There are still some features missing. Sticking to semantic versioning we do not expect any breaking changes in the 1.x releases.