Podman: an alternative to containers with Docker

podman

podman It is a container engine that can be a replacement for Docker. This engine has been developed by the Red Hat company (now owned by IBM) and intends to move it little by little. Will it succeed? Well we'll see…

El open source project it has great ease of use, which is a big draw. Such is the ease that there is an article by Dan Walsh, a Red Hat engineer, in which he shows the steps of a migration to replace Docker with Podman, and they were these:

dnf install -y podman

alias docker=podman

And under that description he ended by saying «Any questions?»With a bit of humor because of how simple it is ...

Besides that, if you are already used to using Docker you don't have to worry too much about the commands, since Podman uses the same ones for the most part. That is, if to run a container you have to use dockerrun, to do it with this other project you have to use podman run. It's that simple to remember the options.

Well, so far everything seems similar. Both projects are good, open source, they work with containers, they are simple, they use the same syntax, etc. But then? What does Podman have to make it worth having? Well, one of the differences is that not based on demons (services in the * nix world).

As you know, Docker does have its associated daemon. This demon is unique and centralized, which means that the more containers you use, its complexity will grow and become heavier and heavier. That is why Red Hat has decided to create this other tool to correct that disadvantage.

In Podman they have decentralized components for container management and thus avoid that broadening of the daemon as occurs in Docker. Those individual components are only used when needed, which will result in less resource consumption.

In addition to that advantage, it has another great advantage. Podman can manage containers in the same way as Docker, but also you can do it with Pods, that is, the drives that are used in Kubernetes. The essential difference between a container and a Pod is that each Pod can in turn contain more than one container.


The content of the article adheres to our principles of editorial ethics. To report an error click here!.

A comment, leave yours

Leave a Comment

Your email address will not be published.

*

*

  1. Responsible for the data: AB Internet Networks 2008 SL
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.

  1.   Miguel Rodríguez said

    That container and container handler will triumph that, in principle, is more efficient in resources, allows the isolation of both the programs and the applications of the system in the most decentralized way possible and finally, it must be able to be installed in different Operating Systems without that affects the construction of the containers, the execution and distribution.

    PS: although not less important, you can add a graphical tool that allows you to perform the same actions as in the console.