This is actually perfect. My main issue with EL distros is that they tend to push podman, which is not a 1-to-1 replacement for docker. This may end up being my default for non-immutable OS installs.
I'm trying to learn Podman because Fedora atomic is the way I want to go right now, but getting firewalld to cooperate is enraging. Are you hitting problems other than that?
Oddly enough: SELinux and file ownership for bind mounts were pretty hellish for me, even with :z. Granted, that's definitely on me (skill issue) for having misconfigured SELinux policies, but docker got out of my way.
Other than that, my gripes about podman have to do with inter-container DNS communication and having to creating systemd services to manage simple container stacks. That last one is a major thorn in my side because the podman CLI used to have a simple command to generate the systemd file for you, but they're getting rid of it.
I run containers locally for basic dev work and, on occasion, deploy simple self-hosted services. In both of those cases, I find Podman to be an unnecessary hindrance where Docker isn't.
The question is what you are doing that need docker not podman? SELinux? Volume mounts? everything is docker capable, podman able to do it better (minus specific socket that podman.socket doesn't support)
Try deploying the Bitwarden self-hosted stack (official, not Vaultwarden) with Podman and then you'll see that Podman's inter-container DNS isn't up-to-par with Docker's.
Podman is not a perfect replacement for Docker and often times gets in the way.