Hey cvicentiu not sure what you where planning here however I was thinking of a bunch of Dockerfiles that create distro packages into a VOLUME.

From that you can then use separate docker containers to model disto tests that aren't well suited to MTR. Distro tests like install, upgrade, startup/shutdown, mysqld_multi test, systemd multi-instance tests, source page test, debug package tests, galera cluster tests (using docker-compose).

This will provide an in tree basis for package builds (GPL compliance of binary packages - providing build rules), sysadmin ability to create working binary packages (even Debug packages), developers to be able to test in multiple environments locally without waiting on buildbot (or VMs management), and contributors to test packaging fixes without buildbot or VM management.

Of course these would be quite usable by buildbot too.

WIP (with workarounds to leave the sourcedir as read only - oh debian you are so ugly):
https://github.com/grooverdan/mariadb-server/tree/10.3-dockerfiles

Hi danblack

The idea is to try a KVM replacement, with images that have the packages embedded, however their actual creation process is entirely visible in a Dockerfile. These images can be published to a local (or remote) repository and will be used to guarantee an always identical and clean run. The server sources can be built in docker VOLUMES and shared between images to improve performance.

Separate distro specific tests are also part of the scope, but will be used at a later date. Your input is greatly appreciated and I'll have a look at your dockerfiles for ideas for sure.

Duplicate of MDEV-12508.