Discover Podman, a next-generation container engine that manages containers rootlessly and provides extra layers of exceptional security unavailable in Docker and other container platforms. In Podman in Action you will learn how to:

Build and run containers in rootless mode Develop and manage pods Use SystemD to oversee a container's lifecycle Work with the Podman service via Python Keep your containers confined using Podman security features Manage containerized applications on edge devices

Podman in Action shows you how to deploy containerized applications on Linux, Windows, and MacOS systems using Podman. Written by Daniel Walsh, who leads the Red Hat Podman team, this book teaches you how to securely manage the entire application lifecycle without human intervention. It also demonstrates how, with Podman, you can easily convert containerized applications into Kubernetes-based microservices. about the technology Podman is a daemonless container engine that lets you build and run containers on all Linux distributions, Windows, and MacOS. It supports the fork exec model for running containers, which allows for better integration with a system and makes it easier to run rootless. It also boasts unique advanced features, such as the ability to create and run Pods that are similar to Kubernetes, and execute Kubernetes YAML. And if you're not ready to completely move on from Docker, Podman can run as a service and support the Docker API in a way that works with docker-compose and docker-py. about the reader For developers or system administrators experienced with Linux and the basics of Docker.

Author: Daniel Walsh
Binding Type: Paperback
Publisher: Manning Publications
Published: 01/26/2023
Pages: 310
Weight: 1.54lbs
Size: 9.21h x 7.32w x 0.63d
ISBN: 9781633439689

About the Author
Daniel Walsh leads the team that created Podman, Buildah, Skopeo, CRI-O and friends. Dan is a senior distinguished engineer at Red Hat, which he joined in 2001, and he has worked in the computer security field for over 40 years. He is sometimes referred to as "Mr SELinux", after leading the development of SELinux at Red Hat prior to leading the container team.