Hi,
First of all, thank you for maintaining this project.
We were looking for a simple Borg server to receive SSH backups from a remote Nextcloud AIO installation running on another TrueNAS server, and your image turned out to be exactly what we needed.
Our setup
- Source: Nextcloud AIO running on TrueNAS Community Edition
- Destination: Remote TrueNAS Community Edition
- Connection: Tailscale (SSH over a private tailnet)
- Borg server:
horaceworblehat/borg-server
The setup itself was straightforward and worked very well once we identified the issue below.
The problem
Initially we deployed the container using the latest tag.
At the time of writing, latest points to 2.8.7, which contains:
Current Nextcloud AIO releases are still using Borg 1.4.4 for backups.
When trying to create the first backup, Nextcloud AIO failed immediately with:
Connection closed by remote host.
Is borg working on the server?
This initially made us think there was a problem with the SSH configuration, permissions or authorized_keys, but after quite a bit of troubleshooting we discovered that the real cause was the Borg version mismatch between client and server.
What solved the problem
We changed the container image from:
horaceworblehat/borg-server:latest
to:
horaceworblehat/borg-server:2.8.6
which contains:
After that single change, everything worked immediately.
Our first backup (~489 GB) completed successfully in about 2 hours 47 minutes, and subsequent incremental backups completed in about 1 minute thanks to Borg deduplication.
We also confirmed that no special configuration was required. The following setup worked perfectly:
authorized_keys
restrict,command="borg serve --restrict-to-path /home/borg/backups"
BORG_SERVE_ADDITIONAL_ARGS
Suggestion
Since Borg 1.4.5 is currently the latest stable Borg release, we believe that the latest image would ideally use that version, unless there is some incompatibility or another reason preventing it.
Because Borg 2 is still in beta, and software such as Nextcloud AIO currently depends on Borg 1.4.4, users deploying the container with the default latest tag can run into compatibility issues without realizing the cause.
If using Borg 1.4.5 for latest is not possible, perhaps the README could at least mention that latest currently contains Borg 2 beta and may not be compatible with clients expecting Borg 1.4.
Thanks again for the great project. Apart from this version mismatch, the container worked perfectly for our use case and made it very easy to implement remote Borg backups between two TrueNAS systems over Tailscale.
Hi,
First of all, thank you for maintaining this project.
We were looking for a simple Borg server to receive SSH backups from a remote Nextcloud AIO installation running on another TrueNAS server, and your image turned out to be exactly what we needed.
Our setup
horaceworblehat/borg-serverThe setup itself was straightforward and worked very well once we identified the issue below.
The problem
Initially we deployed the container using the
latesttag.At the time of writing,
latestpoints to 2.8.7, which contains:Current Nextcloud AIO releases are still using Borg 1.4.4 for backups.
When trying to create the first backup, Nextcloud AIO failed immediately with:
This initially made us think there was a problem with the SSH configuration, permissions or
authorized_keys, but after quite a bit of troubleshooting we discovered that the real cause was the Borg version mismatch between client and server.What solved the problem
We changed the container image from:
to:
which contains:
After that single change, everything worked immediately.
Our first backup (~489 GB) completed successfully in about 2 hours 47 minutes, and subsequent incremental backups completed in about 1 minute thanks to Borg deduplication.
We also confirmed that no special configuration was required. The following setup worked perfectly:
authorized_keysBORG_SERVE_ADDITIONAL_ARGSSuggestion
Since Borg 1.4.5 is currently the latest stable Borg release, we believe that the
latestimage would ideally use that version, unless there is some incompatibility or another reason preventing it.Because Borg 2 is still in beta, and software such as Nextcloud AIO currently depends on Borg 1.4.4, users deploying the container with the default
latesttag can run into compatibility issues without realizing the cause.If using Borg 1.4.5 for
latestis not possible, perhaps the README could at least mention thatlatestcurrently contains Borg 2 beta and may not be compatible with clients expecting Borg 1.4.Thanks again for the great project. Apart from this version mismatch, the container worked perfectly for our use case and made it very easy to implement remote Borg backups between two TrueNAS systems over Tailscale.