Tests performing PROVISION_HOW=container use a wide array of containers, both official ones and custom ones as well. The goal of this ticket is to level the playfield and make the situation more predictable, especially when it comes to various requirements tmt has.
Collect a list of images to test against. The list would start with well-known official images - fedora:rawhide, centos:stream9, etc. Then, based on recent discussions and issues, we will need to add images that:
use non-privileged user & have password-less sudo configured,
emulate ostree environment,
include repository metadata - Ubuntu needs apt-get update, others would benefit from not downloading repo data all the time,
contain the default shell,
and let's see what else we find out.
We would have a set of Container files, to prepare our "test" images, and run podman build for all of them from a make target. It is expected that, in the case of recent distros like rawhide, the actual changes made to the image would be minimal. Eventually, we would end up with the whole set of "test" images, some very close to the original, upstream ones, some enhanced e.g. with the non-privileged account and sudo configuration.
tmt tests would then use these images only: there would be no guessing in a test whether registry.fedoraproject.org/fedora:latest or quay.io/fedora:latest should be used, because the only allowed would be localhost/tmt/fedora/rawhide:latest, for example. We would use the same battery of tests in functional tests and in unit tests, for provisioning or package manager testing, and so on.
Tests performing
PROVISION_HOW=containeruse a wide array of containers, both official ones and custom ones as well. The goal of this ticket is to level the playfield and make the situation more predictable, especially when it comes to various requirements tmt has.Collect a list of images to test against. The list would start with well-known official images -
fedora:rawhide,centos:stream9, etc. Then, based on recent discussions and issues, we will need to add images that:sudoconfigured,ostreeenvironment,apt-get update, others would benefit from not downloading repo data all the time,We would have a set of
Containerfiles, to prepare our "test" images, and runpodman buildfor all of them from amaketarget. It is expected that, in the case of recent distros like rawhide, the actual changes made to the image would be minimal. Eventually, we would end up with the whole set of "test" images, some very close to the original, upstream ones, some enhanced e.g. with the non-privileged account and sudo configuration.tmt tests would then use these images only: there would be no guessing in a test whether
registry.fedoraproject.org/fedora:latestorquay.io/fedora:latestshould be used, because the only allowed would belocalhost/tmt/fedora/rawhide:latest, for example. We would use the same battery of tests in functional tests and in unit tests, for provisioning or package manager testing, and so on.