Podman - Pros, cons and final thoughts - Part 10
Time to wrap this how-to up and summarize some final thoughts with some of the pros and cons from my perspective of diving into the world of containers and particular podman.
Getting started with containers is not as straight forward as some might think, there is a lot of planning beforehand that needs to be done and going back and tweaking things here and there do not often work on an already running environment.
So planning ahead and really think about how you want to run them and where to store the data is essential before starting your first containers, a test environment is a good place to start where you can start over as many times as needed before getting into running them in production.
In this how-to we covered the base level of things to know about getting started with podman in rootless mode. There are wastly more settings that can be used for tweaking and setting up a container environment according to your needs.
- More secure when running in rootless mode.
- Can split containers & pods between user accounts.
- No daemon running at root level at all.
- Less unused system resources in contrast to running full-blown servers.
- Hard to fine-tune after environment is up and running.
- Steep learning curve.
- No clustering / failover management.
So Have you decided?, yes or no to containers...
Whether you choose to run podman as rootless or rootful is up to you and your personal / work needs and requirements, i hope that with this how-to i manage to shed some light on your path forward into the world of containers and in some ways to better understand it.
For me, writing this how-to was and is a journey since i pretty much started writing it a few days into my own journey, and i have learned a great deal and will continue my way into the container world and will share more things along the way with you.