Hi,
sorry for slow responses. My attention is all over the place lately...
And rather worryingly, backups are not high on the list :-D
Quickly on docker: My primary reason is to reduce mess in the OS,
especially since NAS is supposed to run also other things. And it makes
moving between different HW easier, which I actually successfully
employed even with BackupPC.
"I started to notice" was a bit lyrical expression, sorry about that
:-), I started noticing it while I was trying to figure out why BPC does
not run out of sudden. Also, I saw the same error associated with other
files, like when I got BPC half-way running with the host configuration
files. Googling lead me to mentioning to similar error in other
projects, from which I concluded, that it might be an issue with Perl
version or something.
I did read the scripts within the repository.
The configure.pl is run from with in files/entrypoint.sh, line 58. From
what I can see it basically set paths to stuff. As far as I can tell,
the configure.pl is stock from BPC repository.
I have now some hints, that there are problems outside BPC. I will let
you know if I find something interesting...
Jan
On 13. 08. 23 21:13, Kenneth Porter wrote:
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/
_______________________________________________
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/
