kci_docker

[gctucker]

Add a kci_docker tool to produce a new set of Docker images using Jinja2 templates. This is needed in order to provide the flexibility required when running builds and tests in Kubernetes, and to facilitate producing images with special combinations of tools for local development.

See the README on the incoming branch: https://github.com/gctucker/kernelci-core/tree/kci_docker/config/docker-new#readme

The tree of files looks like this:

docker-new
├── base
│   ├── clang.jinja2
│   ├── debian.jinja2
│   ├── host-tools.jinja2
│   └── python.jinja2
├── clang-11.jinja2
├── clang-12.jinja2
├── clang-13.jinja2
├── clang-14.jinja2
├── clang-15.jinja2
├── fragment
│   ├── azure-cli.jinja2
│   ├── gcloud.jinja2
│   ├── kernelci.jinja2
│   ├── kselftest.jinja2
│   ├── kubernetes.jinja2
│   └── kunit.jinja2
├── gcc-10-arc.jinja2
├── gcc-10-arm64.jinja2
├── gcc-10-arm.jinja2
├── gcc-10-armv5.jinja2
├── gcc-10-mips.jinja2
├── gcc-10-riscv64.jinja2
├── gcc-10-x86.jinja2
├── k8s.jinja2
├── kci_docker
├── kernelci.jinja2
├── README.md
└── requirements.txt

[gctucker]

Things to do before this can replace the current docker directory (as follow-up PRs):

• add missing images: qemu, debos, cros-*
• add support for building with caching disabled
• update automated build & push to use the new image names
• update Jenkins to use new naming convention

[gctucker]

Tested OK on staging with new pipeline and KUnit (gcc-10 x86).

The full set of images will be tested when the other parts of the code have been updated to use the new images on staging.