<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Podman :: Tag :: Full Stack DevOps The Architect’s Log</title><link>https://fullstackdevops.eu/tags/podman/index.html</link><description/><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 06 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://fullstackdevops.eu/tags/podman/index.xml" rel="self" type="application/rss+xml"/><item><title>Day 6: Podman Containers alternative to Docker</title><link>https://fullstackdevops.eu/100-days/006-podman/index.html</link><pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate><guid>https://fullstackdevops.eu/100-days/006-podman/index.html</guid><description>Table of contents Containers INtroduction Why Podman? Breaking the Daemon Monopoly The Killer Feature: Rootless by Design Podman + Systemd: The DevOps Secret Weapon The “Zero-Registry” Workflow Performance Comparison Conclusion: If you need Containers, use podman Containers INtroduction If Day 5 of 100 days of FullStack DevOps was KVM Virtualization, Day 6 is about containers with Podman. Usually on a VM or VPS (we’ll get to it on day 7!) we want to run software, if we can’t run self contained apps directly under systemd (or your favorite init system) we’ll have to consider running our software in containers for ease of use. We’ll get back to virtualization automation in future days.</description></item></channel></rss>