<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Podman on M1CH's Log</title><link>https://blog.m1ch.eu/tags/podman/</link><description>Recent content in Podman on M1CH's Log</description><generator>Hugo</generator><language>en-us</language><copyright>Michael Klamminger</copyright><lastBuildDate>Thu, 27 Nov 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.m1ch.eu/tags/podman/index.xml" rel="self" type="application/rss+xml"/><item><title>gorgeOS-Cloud</title><link>https://blog.m1ch.eu/posts/20251127-bootc-cloud-image/</link><pubDate>Thu, 27 Nov 2025 00:00:00 +0000</pubDate><guid>https://blog.m1ch.eu/posts/20251127-bootc-cloud-image/</guid><description>&lt;p&gt;In the &lt;a href="https://blog.m1ch.eu/posts/20251122-bootc-tweeks"&gt;last post&lt;/a&gt; I walked through the base image that every one of my servers shares.
This time I want to look at the first layer on top of it: the &lt;strong&gt;cloud image&lt;/strong&gt;, which adds everything a virtual machine running in a hypervisor environment needs.&lt;/p&gt;
&lt;p&gt;The full source is in my &lt;a href="https://codeberg.org/m1ch/gorgeOS"&gt;gorge.os&lt;/a&gt; repository.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="layered-images"&gt;Layered images&lt;/h2&gt;
&lt;p&gt;One of the things I really like about BootC is that you can layer images just like you layer application containers. The cloud image simply starts from the base:&lt;/p&gt;</description></item><item><title>How I tweak my bootc base image</title><link>https://blog.m1ch.eu/posts/20251122-bootc-tweeks/</link><pubDate>Sat, 22 Nov 2025 00:00:00 +0000</pubDate><guid>https://blog.m1ch.eu/posts/20251122-bootc-tweeks/</guid><description>&lt;p&gt;In the &lt;a href="https://blog.m1ch.eu/posts/20251114-bootc-motivation"&gt;last post&lt;/a&gt; I explained why I decided to switch to BootC for all my servers.
This time I want to walk through what I actually put into my base image - the packages, the config files, and the custom services that make every host feel like home.&lt;/p&gt;
&lt;p&gt;The full source is in my &lt;a href="https://codeberg.org/m1ch/gorgeOS"&gt;gorge.os&lt;/a&gt; repository.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="the-containerfile-structure"&gt;The Containerfile structure&lt;/h2&gt;
&lt;p&gt;Before getting into what&amp;rsquo;s in the image, I want to explain &lt;strong&gt;how&lt;/strong&gt; I put things into it. The Containerfile is split into three stages: package management, file placement, and service activation.&lt;/p&gt;</description></item><item><title>The motivation to use BootC</title><link>https://blog.m1ch.eu/posts/20251114-bootc-motivation/</link><pubDate>Fri, 14 Nov 2025 11:06:14 +0100</pubDate><guid>https://blog.m1ch.eu/posts/20251114-bootc-motivation/</guid><description>&lt;p&gt;I have a fair amount of servers that I&amp;rsquo;m (co-)responsible for. To make my life easier I tried serveral managent tools to do the common tasks for all servers as smooth as possible.&lt;br&gt;
The two tools I mainly use at the moment are &lt;strong&gt;ansible&lt;/strong&gt; and &lt;strong&gt;cloud-init&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Cloud-init is a great tool to spin up a new server, or to resore an existing one.&lt;br&gt;
ansible is great to do common tasks, like updating servers, installing packages to multiple hosts, but when it comes to thinks like adding a systemd-service to just a view hosts, it never felt natural to me.&lt;/p&gt;</description></item></channel></rss>