<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Quadlet on Ilan Cohen</title><link>https://ilanco.dev/tags/quadlet/</link><description>Recent content in Quadlet on Ilan Cohen</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 13 May 2025 08:03:44 +0300</lastBuildDate><atom:link href="https://ilanco.dev/tags/quadlet/index.xml" rel="self" type="application/rss+xml"/><item><title>Starting Containers in a Pod and with a Network using Podman Quadlets</title><link>https://ilanco.dev/blog/quadlet-pod-networking/</link><pubDate>Tue, 13 May 2025 08:03:44 +0300</pubDate><guid>https://ilanco.dev/blog/quadlet-pod-networking/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;While researching a method to auto-start Podman containers, I quickly stumbled upon Podman Quadlets. After some research and investigation, I went ahead
and created the Quadlet configuration files for the Pod, Network and Containers. Unfortunately, the containers did not listen to the correct ports defined in the Pod.&lt;/p&gt;
&lt;h2 id="what-are-quadlets"&gt;What are Quadlets?&lt;/h2&gt;
&lt;p&gt;From the Podman documentation:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Podman supports building and starting containers (and creating volumes) via systemd by using a systemd generator. These files are read during boot (and when systemctl daemon-reload is run) and generate corresponding regular systemd service unit files. Both system and user systemd units are supported.&lt;/p&gt;</description></item></channel></rss>