Run e2e tests for docker provider on CI

[wainersm]

Let's make the recent added e2e tests for docker running as part of CI (nightly and PR).

This way we will be able to test generic process-user-data as the libvirt CI doesn't cover that (libvirt uses cloud-init). Also if we managed to run with CRI-O, bonus points, as we don't have any CI for peer pods with CRI-O.

Depends on:

• ci: podvm-mkosi: workflow not working correctly #1949 - build mkosi images

Cc @stevenhorsman @bpradipt

[stevenhorsman]

Given that the docker tests use the mkosi variant of the podvm image, I guess a pre-req for this to to try and get the mkosi image created regularly in the CI. Guess we could start with https://github.com/confidential-containers/cloud-api-adaptor/actions/workflows/podvm_mkosi_image.yaml and make it run on x86 as well as s390x?

That does look like the workflow is failing now, so I've raised #1949 to cover this.

[wainersm]

Hi @stevenhorsman !

Given that the docker tests use the mkosi variant of the podvm image, I guess a pre-req for this to to try and get the mkosi image created regularly in the CI. Guess we could start with https://github.com/confidential-containers/cloud-api-adaptor/actions/workflows/podvm_mkosi_image.yaml and make it run on x86 as well as s390x?

That does look like the workflow is failing now, so I've raised #1949 to cover this.

I never ran the docker provider and so I had that doubt in my mind whether it uses the packer or mkosi variant. Thanks!

I can work on #1949 too if you don't want/cannot.

[stevenhorsman]

I can work on #1949 too if you don't want/cannot.

Choi has worked out a fix, but it's to revert #1923, so it looks like there is some problem with running on ubuntu vs RHEL.