Hello, czw., 27 lut 2020 o 14:48 Sven Hartge <s...@svenhartge.de> napisał(a):
> > Sure, which does not mean any GPL binary distribution was violated, > right? > > No, my assessment was a bit overly hasty, I apologize. > No problem. At the first email I was really afraid that I've made a real issue to project, so I need to solve it as soon as possible. > > > This also means we cannot easily ship the Docker plugin because > during > > the build stage no network access is allowed. > > > The baculatar is not part of Bacula or Bacula Docker Plugin but it is a > > separate Docker container image. Bacula Docker Plugin does not require > > baculatar Docker image to run. It extends plugin features executing this > > container during Docker volume backup. In Bacula Enterprise it is > > distributed as a separate package. > > I think the best action for any distribution would be ship the > baculatar-part as example for the local admin who wishes to create the > needed container image themselves instead of trying to ship anything > inside the packages. > To be honest, I do not understand. :) The binary 'tar' file at docker/baculatar directory was added by mistake during commit session and was not planned to be a part of distribution. The required Docker container image should be built with supplied createimage.sh script. This container will be removed completely when I finish FD<->Plugin<->FD communication protocol which allow to embed Bacula FD in container directly. best regards -- Radosław Korzeniewski rados...@korzeniewski.net
_______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
