Possibility to get borgbackup 1.4.1 binary for arm64 from your docker image?

[garret]

I have a strange request: I have a raspberry pi system and have been using the binary builds of borgbackup provided by https://borg.bauerj.eu for arm64. However, the project has stopped to v1.4.0 and I tried to contact the project owner to help in releasing new updated builds but he/she seems unreachable.

Do you know if it could be possible to extract the binary of borgbackup v1.4.1 from your docker image and make it work on my raspbian installation?

[bbx0]

Technically this would work. The -distroless variant produces a pyinstaller-based folder containing all files needed. It's not a single binary but works the same. Currently, the borg binaries are build without fuse support.

# remove --arch arm64 to pull the image for the native platform
$ docker create --name borg-1.4.1 --replace --arch arm64 ghcr.io/bbx0/borgbackup:1.4.1-distroless
$ docker cp borg-1.4.1:/opt/borg borg-1.4.1
$ docker rm --volumes borg-1.4.1

$ borg-1.4.1/borg.exe --version
borg 1.4.1
$ borg-1.4.1/borg.exe --debug debug info
..
Borg: 1.4.1  Python: CPython 3.11.14 msgpack: 1.1.0 fuse: None [pyfuse3,llfuse]
..

# the binary is named borg.exe but can be linked as borg as needed
$ sudo mv borg-1.4.1 /opt/borg
$ sudo ln -s /opt/borg/borg.exe /usr/local/bin/borg
$ borg --version
borg 1.4.1

I attached the folder: borg-1.4.1-arm64.zip

The challenge is to keep the glibc version in sync. The 1.4 series is build on Debian 12 (bookworm). As long as your version is the same or newer the binaries should work.

I was contemplating producing staticx based binaries to handle the glibc dependency. Maybe I will pick up on that idea, when time allows.

In borgbackup/borg#8265 we also discussed some option to use the docker image as replacement for the binary.

[garret]

Unfortunately, my glibc version is from Debian 11 (so I have a very old version 2.31). I guess my only remaining option is now to use the docker image as "an executable". I have answered that thread you linked with my use case because it was a bit different from the one posted. Maybe could I ask for your help over there and we close this issue?

[garret]

Sorry, hope it is ok to bump the thread for attention. I had replied to this other borg discussion you had mentioned borgbackup/borg#8265 (reply in thread) with a possible solution. I just wanted to confirm if my proposed solution makes sense or if even could make it simpler, like having a /usr/bin/borg with just :

#!/bin/bash

        docker run \
                --name borgbackup \
                --rm \
                --quiet \
                --env=TZ=Europe/Rome \
                --env=TMPDIR=/dev/tmp \
                --volume=/home/myusername/ssd/backup:/home/myusername/ssd/backup \
                bbx0/borgbackup:1.4.1

So, not even mentioning the user field (--user 1001:1001) since borg should be able to handle the permissions properly?