Update Restic to v1.16.2, RClone to v1.64.2 #176
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CoordSpace
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Just a simple Dockerfile update, bringing Resticker and Rclone up to their latest versions.
For Restic, this update brings a fix for a serious zstd-related data corruption bug for users that have compression set to max (which is most of us).
For Rclone, there are various bug and QoL updates for backends like storj, s3, b2, etc that people can benefit from.
I've been running a local (linux-amd64) build of the image for my hourly backups and one cycle of check+prune, everything seems fine so far with max compression and the storj backend.