I am running a bash script after my backup jobs. It notifies me via ntfy.sh (resp. my own instance of it). What I haven’t got yet is how to pass a log of each job to my curl script to attach it to my POST or to inspect it in bash.
I already tried using DUPLICATI__RESULTFILE and got something like /tmp/dup-ec8c287f-9dd4-4d18-9a00-4f53c81074d7, but the file given by the variable is never there (and I looked for it in the docker container of course).
I don’t think it matters but I am running Duplicati as a docker container on an Ubuntu host.
I’m glad you found a solution, and my comment is script-oriented, but when and how is this:
I don’t use Docker, but I didn’t think run-script-after could look anywhere but in container.
If you’re looking manually, you’re probably too late but how do you know file name to look for?
Regardless, Windows run-script-after gives the expected result. A result file is temporary:
Hi, the variable DUPLICATI__RESULTFILE contains the file path for the log file AFAIK. If I run my script, a path like /tmp/dup-ec8c287f-9dd4-4d18-9a00-4f53c81074d7 is given, but the file isn’t there in the container’s /tmp directory. As the whole duplicati application is running in the docker container, the file can certainly not be created in the host’s /tmp (where I looked for it nevertheless just to be sure). Copying it in the script also failed as the file was not found, I tried that already.
You’re still not saying when and how. Is this a manual run or a run by run-script-after?
Environment variables provided to run-script-after script are meant for use in that run.
If you can confirm that this was run-script-after option, I guess I can try Linux but not Docker.
Tested equivalent script on 2.2.0.0 on Linux Mint 21.3 (a Ubuntu derivative).
It works. My cp during script got results file. Afterwards, results file is gone.
If I break the script by asking to copy a known missing file, I get the warning:
Warning while running test1
2025-11-11 07:33:13 -05 - [Warning-Duplicati.Library.Modules.Builtin.RunScript-StdErrorNotEmpty]: The script “/tmp/resultfile.bash” reported error messages: cp: cannot stat ‘/truly_missing’: No such file or directory
On old UI, this is a yellow popup. On new UI, open Notifications in bottom right.
As message describes, this is just reporting whatever stderr got, here from cp.
Is this the style of warning you saw, except with plausible result file /tmp/dup_*?
What Docker image is used here? LinuxServer chose an odd temp file location.