Improve TMT user experience on SilverBlue system

[jkonecny12]

When you are on SilverBlue system you are trying to avoid adding packages as layers to the system. So, it's great that you have podman example in the documentation but you can't use this for running the tests if they using container or VM. Could you please improve this experince?

Pain points I saw now:

• The install example will not mount existing project directory.
• The container tests won't work out of the box.
• The VM tests won't work out of the box. (not tested but without access to /dev/kvm it won't work)

The best option would be to have a working Toolbx image, however, I guess that is not doable because it's always rootless and you probably need privilege and rootfull container.

[thrix]

Thanks for filing, I have also Silverblue on my refreshed laptop, so I believe I can try to come up here with some solutions.

[jkonecny12]

If I run the existing container test with: podman run --privileged -it --rm -v .:/my_project:z quay.io/testing-farm/tmt-all bash the output is:

stderr (1/1 lines)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Error: 'overlay' is not supported over overlayfs, a mount_program is required: backing file system is unsupported for this graph driver

Failed to check for container image 'fedora:rawhide'. Reason: Command returned '125'.

[jkonecny12]

Another great possibility would be to use flatpak-spawn for running working with the podman outside of the container?

Not sure if that is doable, never used that command :stuck_out_tongue_winking_eye: .

[frantisekz]

• The VM tests won't work out of the box. (not tested but without access to /dev/kvm it won't work)

Addressed in https://copr.fedorainfracloud.org/coprs/frantisekz/testcloud-wip/ ( https://pagure.io/testcloud/pull-request/115# ), updated tmt build will be submitted there later today.

On missing /dev/kvm, testcloud will now fall back to TCG even on x86.

[jkonecny12]

I wasn't aware of the test cloud, it looks great!

However, it needs to be documented. If I understand it correctly it needs user in a testcloud group which is not that straight forward on SB right now.

Or is the testcloud used even now by the TMT and you are just extending it?

[jkonecny12]

I think that the best solution to this issue would be:

• quay.io/testing-farm/tmt-* to support podman in podman solution
• add --device /dev/kvm (or how it is correctly used?) to the container parameters in the documentation

[thrix]

So a small update here, I use tmt in toolbox, and that works well, except container provisioner.

[jkonecny12]

Would it be working if we use host-spawn as podman executable?

[jkonecny12]

For some reason it doesn't seem to work. Not sure why, I can try to investigate later.

[thrix]

Some additional news, I have a patch for also supporting container provisioner :)