December 27, 20214 yr Author UPDATE Vorta2 = 1.0 (2021-12-27) - Added new template of Vorta (Vorta2), but this time using latest Vorta (0.8.2) and Borg (1.11.17) versions.
December 27, 20214 yr Author On 12/18/2021 at 11:05 AM, Hotsoupie said: I installed the docker container yet when I try to generate a SSH key through the GUI I got no luck. After pressing the "Generate and copy to Clipboard" button nothing happends. I checked the logs, reinstalled the container (also deleted the folder) and yet no luck either. Tried it on multiple devices through vnc. Any possible solution? Hello, first, sorry for the late reply. Then, about creating a SSH key for the repo, while creating the repo, I have to say that I didn't have any problem during this process. What I have done, is just create the repo by proding a passphrase to it and left all other options (advanced tab) untouched. Edited December 27, 20214 yr by SmartPhoneLover
December 27, 20214 yr Thanks for the V2 docker. The previous docker when you selected a folder, /locations would be the default selection. Can this be updated?
December 27, 20214 yr Author Just now, kri kri said: Thanks for the V2 docker. The previous docker when you selected a folder, /locations would be the default selection. Can this be updated? Yes, I know that. Something has changed when this new user created the image, but don't know what exactly. But, it stills being available from within the container, if you leave the 'Container' paths as them are. Just navigate to the '/locations' path manually.
December 27, 20214 yr Yep, I was able to find it, was just letting you know. Thanks again for the containers.
December 27, 20214 yr Author UPDATE Vorta2 = 1.1 (2021-12-27) - New: added USER_ID and GROUP_ID variables, so you can handle permissions more accordingly.
December 27, 20214 yr Author On 12/10/2021 at 9:27 AM, sturmstar said: Hi! Thank you very much for your docker. I like it very much. I just have one question - would it be possible to change the permissions after a backup-run? I'm asking because I would like to upload the archive-files with another (rclone)-container - but the other docker doesn't have the permission to access the files... Thank you so much! Hello again, If you still using the other Vorta template, I would suggest you to try the last one I uploaded (Vorta2) which is based on latest Vorta/Borg version. Also, thanks to a collegue from Telegram (UnRAID_ES), now Vorta can create backup files without problems (permission issues), by applying a little workaround but within Vorta itself. To apply custom permissions (chmod) to backups... 1. Go to 'Schedule' tab (Vorta). 2. Add the 'chmod 777 -R /locations/TO' cmd into the second Shell Commands's field. 3. Done. The above setting will allow Vorta to change file permissions after creation.
December 28, 20214 yr 7 hours ago, SmartPhoneLover said: Hello again, If you still using the other Vorta template, I would suggest you to try the last one I uploaded (Vorta2) which is based on latest Vorta/Borg version. Also, thanks to a collegue from Telegram (UnRAID_ES), now Vorta can create backup files without problems (permission issues), by applying a little workaround but within Vorta itself. To apply custom permissions (chmod) to backups... 1. Go to 'Schedule' tab (Vorta). 2. Add the 'chmod 777 -R /locations/TO' cmd into the second Shell Commands's field. 3. Done. The above setting will allow Vorta to change file permissions after creation. Hi. Just installed the v2 and added the chmod 777 into the field. I will tell you later if it works this way - but why shoudn't it. Thank you. Best regards
December 28, 20214 yr Author UPDATE Vorta2 = 1.2 (2021-12-28) - Other: disable Privileged option, as the container doesn't need it. Edited December 28, 20214 yr by SmartPhoneLover
December 29, 20214 yr On 12/28/2021 at 7:20 AM, sturmstar said: Hi. Just installed the v2 and added the chmod 777 into the field. I will tell you later if it works this way - but why shoudn't it. Thank you. Best regards It worked perfectly. Thank you. If I could make another wish or "feature request" - implement a possibility to send notifications (mail) for different events like "backup successfull", "backup failed" usw. But as I said - that's only a wish. Best regards
December 30, 20214 yr Author 3 hours ago, Greygoose said: SmartPhoneLover, What is the difference between Vorta and Vorta 2? If you check the main thread, the 'Vorta' template is based on a deprecated docker image (old Vorta/Borg version), and 'Vorta2' is based on another different docker image, from another user, which is based on the latest version of Vorta and Borg. Other than that, the differences between both are just these.
December 30, 20214 yr Author On 12/29/2021 at 7:33 AM, sturmstar said: If I could make another wish or "feature request" - implement a possibility to send notifications (mail) for different events like "backup successfull", "backup failed" usw. There's a user from Telegram that made a little script that does exactly that, but with Telegram notifications (bot), not email. Maybe, could be done the same with email API. Wjen I test it, I will post it here, don't worry.
December 30, 20214 yr 2 minutes ago, SmartPhoneLover said: There's a user from Telegram that made a little script that does exactly that, but with Telegram notifications (bot), not email. Maybe, could be done the same with email API. Wjen I test it, I will post it here, don't worry. Sounds good - similar to the Telegram bot which is integrated in unraid - and I'm using...
January 3, 20224 yr Anyone know how to easily move Sources from one repo to another? I have quite a few external drives I back up to, and the sources all are the same. I can move them one-by-one, but looking for a quicker way if possible.
January 5, 20224 yr Firstly thanks for providing this!!! I have a weird issue (and I assume I can use vorta2 to backup my Unraid instance). I have the volumes mounted as below; volumes: - /mnt/user/appdata/vorta2/config:/config - /mnt/user/appdata:/config/locations/FROM/appdata - /mnt/user/photos:/locations/FROM/photos - /mnt/user/storage:/locations/FROM/storage - /mnt/user/system:/locations/FROM/system - /boot:/locations/FROM/boot - /mnt/remotes/nas:/config/locations/TO But the container doesn't start and stalls at [cont-init.d] 00-take-config-ownership.sh: executing... Now I have nailed it down to the mounting of /mnt/user/appdata. Is there any way around this?
January 12, 20224 yr I am using the unassigned devices. It appears my repo on said unassigned device (external ssd) does not load until I reboot the vorta2 docker. Is there anything I can do to automatically run the backup when a device mounts?
January 18, 20224 yr Where does this docker store it's ssh public key? I'd like to connect to an already existing Borg backup on a remote host. My connection string (from the command line) is like this: ssh://[email protected]:10222/mnt/user/borgbackup This assumes that I have the local ssh key in the authorised hosts file on the remote system, but I can't see where this docker's ssh public key is located. Edited January 18, 20224 yr by ThatDude
January 24, 20224 yr The issue I found with this container re: ssh is that there is no home folder setup for the app user. So when creating ssh keys they get written to /dev/null/.ssh by default (go into the ether). This is also the location that known hosts should be, so even if you put ssh keys somewhere else when vorta/borg attempts to ssh to borgbase it can't save the remote host into the known hosts file. To rectify I jumped into the Vorta2 container: docker exec -it Vorta2 sh Then setup /config as the home directory for the app user (that way keys and known hosts would live in my appdata/Vorta2/.ssh folder) /tmp # usermod -d /config app To check it worked you can see where users home folders are located by running this in the container: getent passwd ... app:x:99:100::/config:/sbin/nologin ... From there I could create ssh keys, select them from dropdown, and connect to borgbase with authorized hosts and keys being stored in /config/.ssh My vorta appdata folder now has the following in its .ssh folder: Hope that helps. Edited January 24, 20224 yr by Jonathon
February 8, 20224 yr Hello, Can the Vorta 2 docker be updated to include this so we do not need to manually perform it? Thank you! On 1/24/2022 at 5:32 PM, Jonathon said: The issue I found with this container re: ssh is that there is no home folder setup for the app user. So when creating ssh keys they get written to /dev/null/.ssh by default (go into the ether). This is also the location that known hosts should be, so even if you put ssh keys somewhere else when vorta/borg attempts to ssh to borgbase it can't save the remote host into the known hosts file. To rectify I jumped into the Vorta2 container: docker exec -it Vorta2 sh Then setup /config as the home directory for the app user (that way keys and known hosts would live in my appdata/Vorta2/.ssh folder) /tmp # usermod -d /config app To check it worked you can see where users home folders are located by running this in the container: getent passwd ... app:x:99:100::/config:/sbin/nologin ... From there I could create ssh keys, select them from dropdown, and connect to borgbase with authorized hosts and keys being stored in /config/.ssh My vorta appdata folder now has the following in its .ssh folder: Hope that helps.
February 27, 20224 yr Hi, Vorta2 image author here. Because of the attention this has received, the image has been made a part of the official borgbase git repos at https://github.com/borgbase/vorta-docker The new location for the images will be ghcr.io/borgbase/vorta-docker I believe that the issue is fixed in the latest image available there. The fix is not available at the original repo location and I've put up a notice about the new location there as well. Thanks, Mark
February 27, 20224 yr Author 21 minutes ago, Ranbato said: Hi, Vorta2 image author here. Because of the attention this has received, the image has been made a part of the official borgbase git repos at https://github.com/borgbase/vorta-docker The new location for the images will be ghcr.io/borgbase/vorta-docker I believe that the issue is fixed in the latest image available there. The fix is not available at the original repo location and I've put up a notice about the new location there as well. Thanks, Mark Hello! First of all, thank you very much for your work, it is awesome! Thank you for creating the image 🤝😉. Regarding to the changes on the repo, I will change the template to point it to the new repo. Edited February 27, 20224 yr by SmartPhoneLover
February 27, 20224 yr 1 hour ago, Ranbato said: Hi, Vorta2 image author here. Because of the attention this has received, the image has been made a part of the official borgbase git repos at https://github.com/borgbase/vorta-docker The new location for the images will be ghcr.io/borgbase/vorta-docker I believe that the issue is fixed in the latest image available there. The fix is not available at the original repo location and I've put up a notice about the new location there as well. Thanks, Mark This is great, but... You just made obsolete my 2 weeks old video tutorial!!! XD I found the usermod workaround by myself, and posted it as part of my guide. No longer needed, it seems. Now seriously, thank you for your container. Lots of users from the Spanish community have started to use Borg recently thanks to your container. Keep on with your great work! 👏
February 28, 20224 yr Author UPDATE 1.3 (2022-02-28) - Other: Changed template repository URL to point it to the official one (ghcr.io/borgbase/vorta-docker:latest). - Other: 'Vorta2' is now 'Vorta' template on CA repo. - Other: Paths and variables were updated to match the new docker image.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.