Hi,
so, first, a really good job has been done to lock down TrueNAS and not allowing modifications to system path, kudos on that!
Unfortunately, that prevents me from using TrueNAS as Borg repository.
I was using “developer mode” to install borg on TrueNAS, and that is as simple as it can possibly be - enable dev mode, install borg with apt and voilá!
Now I’d wish for a cleaner solution that also is persistent across upgrades, avoiding developer mode (because it is not supported!).
Borgmatic on client system expects “borg” binary to be in the PATH, but PATH variable cannot be changed for non-interactive shell.
In other words, this command works (with standalone borg binary downloaded from internet, not installed via apt)
client# ssh borgbackup@truenas.server /mnt/BACKUP/borg-dir/borg
usage: borg [-V] [-h] [--critical] [--error] [--warning] [--info] [--debug]
…
But this command does not even when ~borgbackup/.bashrc file on Truenas server has PATH updated with /mnt/BACKUP/borg-dir
client# ssh borgbackup@truenas.server borg
bash: line 1: borg: command not found
Installing borg in a docker container is also not great, because I actually want borg to be exposed in TrueNAS.
¯\_(ツ)_/¯