Docker container

[Ranbato]

I've created a beta version of Vorta running in a docker container if anyone wants to play with it.
https://hub.docker.com/repository/docker/marklambert/vorta

Here is a sample snippet of my docker-compose.yaml that I am using to start it up. In the .env file I am setting TZ, USER_ID, and GROUP_ID. I am also defaulting them in the Dockerfile to get around #1125

vorta:
    image: marklambert/vorta
    container_name: vorta
    hostname: storage-vorta
    volumes:
      - /volume1/config/vorta:/config
      - /volume1:/data:ro
      - /volumeUSB1/:/destination
    ports:
      - 5811:5800
    restart: unless-stopped
    env_file:
      - ./.env

For the curious or paranoid, here are all the scripts: borg-vorta.zip

Suggestions and questions welcome

[Ranbato]

I've updated the image to address polkit vulnerability CVE-2021-4034

[Ranbato]

And now Vorta 0.8.3

[BryanWall]

@Ranbato, thank you for publishing this. It's being used on Unraid OS by quite a few people. There's an issue when connecting to the Borg server using SSH key authentication, however. The issue is that the "app" user's home folder isn't being set correctly by export HOME=/config in startapp.sh. Or it might be that Vorta or the ssh client are reading the home folder in /etc/passwd instead of using the environment variable. A temporary fix is to change the user's home folder from inside the container while it's running using usermod. This works because it sets the home folder in /etc/passwd, but when the container is restarted the home folder reverts to /dev/null.

Do you have any thoughts on how to get Vorta/ssh to find the correct home folder or persist the change to the home folder across restarts?

Here's some discussion about the issue:

https://forums.unraid.net/topic/117021-support-smartphonelover-vorta-gui-for-borg-backup/?do=findComment&comment=1089085

[m3nu]

How about making this into a separate git repo? Most Docker containers I work with come in their own repo to discuss improvements. Can be under @Ranbato's user or @borgbase with admin access for him.

I may also be able to help with the home folder thing. Once it's set up properly it will be easier for people to improve on and keep it working. It would also need regular rebuilds to pull in Vorta and base image updates. I can work on both these items, having worked a lot on rootless container setups recently.

[m3nu]

Added this problem as issue in the new repo. borgbase/vorta-docker#3

[Ranbato]

Either works for me. Happy to create a repo on my account or, if you want to make it more official create a repo here and I'll add the Dockerfile.

[m3nu]

Great! Just did some basic setup using your zip file: https://github.com/borgbase/vorta-docker

There is also a workflow to build and publish the image. Can also be triggered manually with our without SSH access for debugging.

This is using GHCR instead of Dockerhub to have it all in one place. So the new image URL is ghcr.io/borgbase/vorta-docker:latest

Also added a small fix to support Borg 1.2.0.

Will be great if someone can test it, as I don't have the setup for Docker GUI apps here.

[Ranbato]

I'll put some notifications on my docker repo pointing to the new location and work out a deprecation timeframe. In the meantime, I'll spend some time this week on the ssh issue and some other cleanup

[Ranbato]

New image is up that fixed the issue for me. PTAL https://github.com/borgbase/vorta-docker/pkgs/container/vorta-docker

[tipitao]

Good morning, I'm deploying the Vorta Backup docker and once the docker is configured, I get the following message: "volumes must be a mapping". I've tried changing the volume configuration by smartlinks, by device and by absolute path but the error in the check continues to appear. My docker compose code is the following:

hostname: XXXXXXXX
cap_add:
- SYS_ADMIN
security_opt:
- apparmor:unconfined
privileged: true
volumes:
- /Nvme/Dockers/vorta/config/:/config
- /Raid5:/data:ro
- /ExternoIntenso/:/Backups
ports:
- 5811:5800
restart: unless-stopped
env_file:
- ./.env

My devices:

Smartink Absulte path Device Comment
/Nvme....................:/srv/dev-disk-by-uuid-074c79d4-a807-4a62-bffc-f24a4d6a26bc /dev/nvme0n1p1 Nvme with dockers config
/ExternoIntenso :/srv/dev-disk-by-uuid-585d6c0b-f667-4d89-9185-bdedfb1c4edf /dev/sdd1 External Usb disk
/Raid5.....................:/srv/dev-disk-by-uuid-83e7b083-1bf0-4435-a953-988afc351b4a /dev/md0 Rad 5 with personal data of users

I would appreciate some light. I will try to find the problem as well.

Regards

[Ranbato]

What version of compose are you using? Are you specifying a compose version in the file?
It seems like maybe there is more to the error string? Like maybe "volumes must be a mapping not an array"?
Some things to try:

• take off the trailing '/'
• Test the mount separately, like in https://docs.docker.com/engine/storage/bind-mounts/ examples
• Try the alternate format https://docs.docker.com/reference/compose-file/services/#volumes

[tipitao]

I have tried removing the "/" from the end and it shows the same error.

/Nvme/Dockers/vorta/config:/config
- /Raid5:/data:ro
- /ExternoIntenso:/Backups
Good afternoon, I'm trying to deploy from Open Mediavault "7.4.8-1 (Sandworm)" with docker version "docker-ce 5:27.3.1-1debian.12bookworm". The docker compose file I'm using is "https://github.com/borgbase/vorta-docker".

Before deploying the docker I have the possibility in OMV to do a docker deployment validation to see if everything is correct and when doing it it already shows me the error "validating /srv/dev-disk-by-uuid-074c79d4-a807-4a62-bffc-f24a4d6a26bc/Dockers/Vorta/Vorta.yml: volumes must be a mapping".

As I have commented I have tried in the volumes section of the compose with Smartlinks, Absolute Paths and Devices. What I don't know is if the mount point should be used for the volume in Vorta's docker compose. I have several dockers deployed and everything has been relatively easy for me. Now I have PiHole, Qbittorrent, Jellyfine, Syncthinc, Watchtowewr, Jdownloader and Emule dockers running, and as I mentioned I am very happy with how it works (with the people who help right away). The truth is that I am just starting with PMV/Linux and I am learning little by little

Regards

[Ranbato]

There is nothing special about Vorta and how it uses the mount points.
Maybe take a multi-step approach.

1. Start up the container with no volumes
2. Add a volume and restart
3. Repeat until you find the problematic mount
4. If none of them work, try temporarily copying a working mount from another container

That may help narrow down the root cause.

[tipitao]

Hi, I've tried commenting out the 2nd and 3rd lines of the complse in the volumes section. Also commenting out the 3 volumes lines and it still shows the same error ".......validating /srv/dev-disk-by-uuid-074c79d4-a807-4a62-bffc-f24a4d6a26bc/Dockers/Vorta/Vorta.yml: volumes must be a mapping".

The last paragraph of the error shows:
: volumes must be a mapping in /usr/share/openmediavault/engined/rpc/compose.inc:893

I have copied part of the volume sections from another container that I have running and it does not work.

I'm a bit confused.

Regards