My takeaway from the last time we discussed this was: 1) To be ASF compliant, we needed to only publish images at official releases 2) There was some ambiguity about whether or not a container image that included GPL'ed packages (spark images do) might trip over the GPL "viral propagation" due to integrating ASL and GPL in a "binary release". The "air gap" GPL provision may apply - the GPL software interacts only at command-line boundaries.
On Wed, Feb 5, 2020 at 1:23 PM Dongjoon Hyun <dongjoon.h...@gmail.com> wrote: > Hi, All. > > From 2020, shall we have an official Docker image repository as an > additional distribution channel? > > I'm considering the following images. > > - Public binary release (no snapshot image) > - Public non-Spark base image (OS + R + Python) > (This can be used in GitHub Action Jobs and Jenkins K8s Integration > Tests to speed up jobs and to have more stabler environments) > > Bests, > Dongjoon. >
