On 8/13/2023 8:34 AM, G.W. Haywood via BackupPC-users wrote:
First off I've never run BackupPC on anything except bare metal. As
far as I can remember I haven't even tried to run it in a VM let alone
using Docker. You're using somebody else's docker installation and I
can imagine that things could go wrong which have nothing to do with
BackupPC itself. By using this form of installation you might be
making it easy to install BackupPC if it works, but I don't think it's
necessarily going to make it easy to troubleshoot things if it doesn't.
Looking at 'Dockerfile' in .../adferrand/docker-backuppc.git makes me
ask more questions than it answers for me.
I concur with the rest of your analysis and questions. But I can see the
value of a Docker image. It's no worse than running on some unusual
Linux distro. Containers and VMs let an app isolate itself from the
package choices of the host OS, relying solely on the kernel. It's why
Snap is making inroads against traditional RPM and dpkg packaging
systems. The older systems are fine for keeping the underlying system
stable, but not so good for apps that use bleeding-edge libraries. The
new container-based packaging helps separate responsibilities between OS
libraries and app libraries.
Of course, the end-user/administrator then has to figure out where to
send problem reports: To the distro/container maintainer or the app
developer. This does look like a packaging issue and not an issue with
the app. So I'd recommend opening an issue on GitHub against the
container project.
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
