podman backend: next steps

[TomasTomecek]

Related #200 #298

• testing, must have
  • make sure the podman tests run and pass in a container (docker so far)
  • run the tests in a podman container (meaning, swap docker for podman)
  • it is possible to invoke podman tests for:
    • rootless mode (su - <unpriv user> -c podman) -- this will likely require to run the tests in a VM since we need new kernel for this, EL7 kernel is old
    • root mode (sudo podman...)
• update documentation
  • README
  • read the docs

Feel free to edit this post and add more.

[rpitonak]

unify test suite: one test suite, multiple backends (this is really an epic)

I think this point deserves own issue.

[srmocher]

I'm interested in taking up this issue (unless someone else is already working on it).

[TomasTomecek]

I already fixed running the tests in CI (they run in a privileged docker container) #330, feel free to change it to a privileged podman container. Since our CI is CentOS 7, we can't utilize user namespaces (given the old el7 kernel) so resolving the rootless mode would be only local when we run it on Fedora on our laptops, but that should be eventually resolved by #329. Docs are needed badly, once we have that, we can probably do a new release.

@srmocher please let us know if you're still interested and we can help you out (but given the holidays, our responses may be delayed)