tgbyte / docker-borg-backup

A dockerized Borg Backup server

docker-borg-backup

A dockerized Borg Backup server. For more information about Borg Backup, an excellent de-duplicating backup, refer to: https://www.borgbackup.org/

Usage

docker run -e BORG_AUTHORIZED_KEYS=<ssh_authorized_key> -e BORG_UID=<uid> -e BORG_GID=<gid> -v <borg_volume>:/var/backups/borg tgbyte/borg-backup

Alternatively, use the Docker orchestrator of your choice.

Caution: Do NOT forget to mount a volume as /var/backups/borg to host the backups. Otherwise your backups will vanish into thin air when you update the Borg container.

To persist the container's SSH host keys across container updates, mount a volume to /var/lib/docker-borg.

Supported Architectures

This image is available for the amd64 and arm64 architectures.

License

The files contained in this Git repository are licensed under the following license. This license explicitly does not cover the Borg Backup and Ubuntu software packaged when running the Docker build. For these components, separate licenses apply that you can find at:

• https://borgbackup.readthedocs.io/en/stable/authors.html#license
• https://ubuntu.com/licensing

Copyright 2018-2023 TG Byte Software GmbH

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

docker-borg-backup's Issues

persist generated ssh host key

Hi, and thanks for your beautiful image!

Do you know how to persist the host ssh key?

Thanks!

CI/CD?

For security reasons, you should automatically build and deliver updates e.g. when the Debian base image you depend on changes/in-cooperates security updates.

I guess, you should do this automatically in a CI/CD. I see no such one setup… so do you use one?

If so, where? If not, I'd strongly suggest that…

WARNING: UNPROTECTED PRIVATE KEY FILE!

Hi,

I am getting this error message in the logs of this container. It appears to be preventing any SSH access. For the past 4 weeks it was running fine until this message appeared without any input from me. Can somebody help?

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0660 for '/etc/ssh/ssh_host_ed25519_key' are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.

I have the container running with Portainer on TrueNAS Scale. SSH key is supplied using a BORG_AUTHORIZED_KEYS environment value.

Debian 11?

docker-borg-backup/Dockerfile

Line 1 in db93474

FROM debian:10

Debian 11 is out there, so maybe you should switch to that?

License?

I just realized I'm using your work, but you didn't put any license, could you correct that please?

Thanks!