Server? Use CRI-O + kube.
CI/CD (that needs to build a container)? Use buildah.
And use skopeo for copying images around when needed
You could argue this makes it more difficult to run containers on the server without kube, and you'd be right. Whether or not that is a bad of red hat to do I'll leave up to others.
build containers to confirm that your build steps all work ok, so Podman + buildah, then you might want to
... push them to a repository to collaborate with a colleague without setting up CI/CD, so Podman + Buildah + skopeo.
Then you might want to execute the containers to test to see whether your code is running ok....
the point I was making didn't relate to running containers on servers where typically things like CI/CD will be part of the process, but to new developers and devops people getting started with containers.
For debian/ubuntu users (of which there are a fair quantity) whilst podman's install process looks like that, I don't see it taking over from Docker any time soon.
Not to mention Windows/OSX users.
Ease of use should not be overlooked when it comes to developer tooling. Podman can be the most technologically advanced solution, but if it's a pain for developers to get going with it, it's not going to replace Docker any time soon...
Is buildah an alternative to Kaniko then?