Podman support

[edigaryev]

The most simplest invocation (in the directory with the .cirrus.yml) looks like this:

cirrus run --container-backend=podman

The Podman backend will also be automatically selected when no Docker daemon is present on the host.

TestResourceLimits had to be disabled when running with Podman backend due to containers/podman#7959.

There are some things that still need to be done before this gets merged:

• Podman socket location auto-detection
• Rename DockerOptions to ContainerOptions and other de-Dockerizations (e.g. 'docker pull' succeeded in 4.2s)

[edigaryev]

@fkorotkov what do you think about moving podmanapi package to a separate repository to avoid huge diff?

[edigaryev]

Rename DockerOptions to ContainerOptions and other de-Dockerizations (e.g. 'docker pull' succeeded in 4.2s)

be8883e and 43f152d.

Podman socket location auto-detection

I'm reading the Podman's API document and thinking that we could probably combine Using the REST API with the Running as a subprocess to get the best of both worlds.

By spawning a podman system service process in containerbackend.NewPodman(), we could get a predictable socket location and provide an experience similar to what Docker does when everything works out of the box.

An additional --podman-binary flag can be provided for development purposes in case putting a custom-built podman binary in PATH is not feasible for some reason.

[fkorotkov]

Looks amazing! What do you think about an option to pass backend as an argument to run command? Something like cirrus run --backend=podman. Or we can do in the follow up PR about running podman binary instead of relying on a running podman service.

[fkorotkov]

I think aliass are not uniques so you can use "tests" in both tasks.

[edigaryev]

Renamed in e908393.

[edigaryev]

What do you think about an option to pass backend as an argument to run command? Something like cirrus run --backend=podman.

Added in b3b9add.

Or we can do in the follow up PR about running podman binary instead of relying on a running podman service.

This was already has been done here in a4d143c.