You can run containerized applications on RHEL by using Podman to eliminate dependencies on a central daemon and improve system security through rootless operation.

The podman-docker package also provides a compatible environment for managing Docker-formatted images while ensuring a smaller system footprint and better isolation.

Red Hat removed the Docker container engine and the docker command from RHEL 8. If you still want to use Docker in RHEL, you can get Docker from different upstream projects, but it is unsupported in RHEL 10.

• You can install the podman-docker package, every time you run a docker command, it actually runs a podman command.
• Podman also supports the Docker Socket API, so the podman-docker package also sets up a link between /var/run/docker.sock and /var/run/podman/podman.sock. As a result, you can continue to run your Docker API commands with docker-py and docker-compose tools without requiring the Docker daemon.
• The podman command, such as, the docker command, can build container images from a Containerfile or Dockerfile. The available commands that are usable inside a Containerfile and a Dockerfile are equivalent.
• When you use podman, you can not use several options available with the docker command, including network, node, secret, service, stack, and swarm. You also cannot use the plugin option because Podman does not support plugins. If you want to rename a container with Podman, you must use rm and then create instead of the rename option. You run subcommands directly in Podman rather than using the container and image options.