Ridding yourself of demons – err um – daemons, with Podman
Docker and Podman are both tools that aim to make it easier to run and manage containers on a host machine. Since Podman is the new kid on the block, you may be wondering how you can switch from Docker to Podman. While technically it is possible to run both Docker and Podman together on the same system, there are very few practical reasons to do this. Since both tools provide the same core capabilities, I would advise you to choose one or the other.
One of the key benefits of switching to Podman is you will inherently lose the daemon that lurked behind the scenes of Docker. You see, Docker relies on a daemon that does all the heavy lifting of managing containers. This may not seem so bad on the surface, but there are some things to be aware of when it comes to this architecture.
For starters, having an extra daemon running in the background means there is one more point of failure. If that dedicated daemon for Docker crashes, you lose all your containers. The additional daemon also increases your attack surface, and because the Docker daemon has root access to the system, any compromise made to the Docker daemon puts your system at greater risk.
This recipe aims to exorcise those demons – err, um – discontinue the use of the Docker daemon. The best thing is, if you aren’t using Docker and you only ever installed Podman, you don’t need to worry about anything – that’s because Podman is rootless by default, and it leverages systemd to manage your containers. systemd is a tried-and-tested system-level daemon that provides an array of system components, including a system and service manager, parallelization capabilities, logging, and utilities to manage and maintain system configuration.
On the other hand, if you were previously using Docker, we’re going to show you how to switch. It’s really quite simple – all you need to do is remove Docker and install Podman.

Getting ready
I’m running on x86-64 bit architecture, but Oracle Linux and Podman also work on Arm. However, it’s important to know that not all containers are compiled in Arm, or vice versa. With that being said, it may be easier to follow this guide using an x86-64 bit CPU:
• Oracle Linux
• Podman

How to do it…

1. Remove Docker by running the following command:

$ sudo dnf remove -y docker-ce docker-ce-cli containerd.io docker-compose-plugin

2. After this, you will be able to install Podman with the following:

$ sudo dnf module install container-tools

3. If you previously added your user to the docker group, you may go ahead and delete that group because it is no longer needed:

$ sudo groupdel docker

Now you’re running containers without the Docker daemon, and by default with Podman, you’re rootless.