Borg 2.0

[modem7]

Putting this issue here so we can keep visibility in case something breaks once it's released.

Version 2.0.0a2 (2022-06-26)

Compatibility notes:

this is a major “breaking” release that is not compatible with existing repos.

You can use “borg transfer” to transfer archives from borg 1.1/1.2 repos to a new borg 2.0 repo, but it will need some time and space.

https://borgbackup.readthedocs.io/en/2.0.0a2/changes.html#version-2-0-0a2-2022-06-26

[witten]

borgmatic already supports Borg 2, but the big challenge for most docker-borgmatic users will be transferring their old Borg 1.x repo to 2.x: https://torsion.org/borgmatic/docs/how-to/upgrade/#borg-1.2-to-2.0

I don't see any reason why that shouldn't be possible from within a container though.

[hugalafutro]

I wanted to try to transfer to v2 repo, but the borg inside the container is 1.2.4 or is there an image with borg 2 inside?

pi@pi-docker:~/docker/borgmatic $ docker compose exec -it borgmatic borgmatic --version
1.7.14
pi@pi-docker:~/docker/borgmatic $ docker compose exec -it borgmatic borgmatic borg -V
borg 1.2.4

[witten]

I don't think there's currently an image with Borg 2 inside. If you wanted to just do that for testing purposes, you could probably run the existing image and then temporarily upgrade it to Borg 2. E.g., exec into the container and install Borg 2 with pip, changing borgmatic's local_path option as necessary to use it. Of course, this would only be temporary, and you'd lose Borg 2 when the container restarted. But it could be good enough for testing stuff out.

[hugalafutro]

@witten Thanks, I thought so. I wouldn't mind trying out the upgrade process, but don't find it feasible if I'd have to upgrade borg inside the container every rebuild too. It's not that I need it or anything isn't working, I just like tinkering with stuff.

[witten]

Totally understood. Note that 2.0 at this point is not recommended for production use, so it'll probably be a little while before it appears in the Docker container.