docker base image targets

[gehoern]

build-deb -> debian package builder base image (e.g buildessentials devscripts debhelper ... with dev user ) build-kernel -> builder for kernel images (what do i need to build nvidia packages or mellanox driver = dkms, kernel-header) slim -> is build.s without any feature plus a lot from the current build container (with slimify on) base -> same as slim without slimify ~alpine~ -> we are posix conform alpine is not targeted "distroless" -> based on gardenlinux but limited the same way as googlecontainertools/distroless (it isn ot on ly one image ... multiple)

[Vincinator]

#547 - but used name build-kernelmodule instead of build-kernel

[Vincinator]

We need a docker registry to also solve the chicken-egg-problem.

• *build.sh requires a build-image container
• build-image container requires a slim base image
• to build aslim base image we require to run *build.shto create a rootfs.tar.xz

To solve the chicken-egg-problem

1. Build a slim image by using a debian slim in build-image, so we can use build.sh to create a rootfs
2. build, and upload our gardenlinux/slim to a registry
3. for future builds we can download the gardenlinux/slim instead of the debian slim image.

and I think it is not necessary to rename the debian slim to gardenlinux/slim

.. PR will follow

[gyptazy]

Hey @gehoern,

I'm closing this one as a DUP to #1387. With #1388 we already have new build targets for general container image support in our build pipeline (the container feature itself has been integrated by #1389).

Within #1390 the artifacts will be pushed to public registries and be used as our internal build image in our own pipeline (#1391). A distroless alike image will be provided by #1392.

Cheers, gyptazy