Hey there,
I have just installed duplicati-agent on an Ubuntu Server 24.04, running on a Raspberry Pi and I have started the duplicati-agent.service with systemctl and it’s running, but when running duplicati-agent run it is runnig in the terminal and not as a daemon. And if I don’t run duplicati-agent run it is not connected in the console.
The machine is registred, so I can create and manage the backup job via the console on https://app.duplicati.com/. But when I close the ssh connection to the Ubuntu Server, of course the instance of the duplicati-agent is terminated, which is not even possible to do with the regualar ctrl-c etc.
I have spend hours trying to read up on this in the documentation, but to no avail, I have a hunch that it might be the preload settings, but they are not even precense in the pure agent installation.
Well - looks like I didn’t read the documtantion thouroghly enough, for anybody needing this it’s in the Using Duplicati with Linux | Duplicati section.
I would say the part about manually having to start/enable the service, if I install a new app, that is expected to be running as a daemon, then I would also expect it to be started/enabled in systemd automatically as part of the installation process. And then make a note about it beeing enabled and how to disenable it if needed.
And maybe change the heading in the documentation where it says Using Remote Management to include the workd Agent, now it’s first visible in the sub-menu and at the end of the heading. And having clear links to using the agent with the various OS’s.
And btw I like the idea of remote management of my backups, would it by any means be possible to have that remote engine running in a docker compose enviornment on a self-hosted server?
