<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
      <title>72p.de - Linux</title>
      <link>https://72p.de</link>
      <description>This is an example description</description>
      <generator>Zola</generator>
      <language>en</language>
      <atom:link href="https://72p.de/tags/linux/rss.xml" rel="self" type="application/rss+xml"/>
      <lastBuildDate>Mon, 18 May 2026 00:00:00 +0000</lastBuildDate>
      <item>
          <title>Using deface on 10 Bit HDR Videos</title>
          <pubDate>Mon, 18 May 2026 00:00:00 +0000</pubDate>
          <author>Unknown</author>
          <link>https://72p.de/posts/deface-10bit/</link>
          <guid>https://72p.de/posts/deface-10bit/</guid>
          <description xml:base="https://72p.de/posts/deface-10bit/">&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;github.com&#x2F;ORB-HD&#x2F;deface&quot;&gt;deface&lt;&#x2F;a&gt; is a script to automatically blur faces.
Its underlying engines &lt;code&gt;onnxrt&lt;&#x2F;code&gt; and &lt;code&gt;opencv&lt;&#x2F;code&gt; are limited to 8-bit processing.
It took me way too long to figure out how to use deface’s capabilities while preserving the full 10-bit color information (I admit, it’s very niche).&lt;&#x2F;p&gt;
&lt;p&gt;That’s why I just want to briefly mention the result here.&lt;&#x2F;p&gt;</description>
      </item>
      <item>
          <title>Upgrading dnf search</title>
          <pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate>
          <author>Unknown</author>
          <link>https://72p.de/posts/dnf-search/</link>
          <guid>https://72p.de/posts/dnf-search/</guid>
          <description xml:base="https://72p.de/posts/dnf-search/">&lt;p&gt;It has always bugged me that &lt;code&gt;dnf search&lt;&#x2F;code&gt; has no indication in the output whether a package is already installed.
In fact, &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;bugzilla.redhat.com&#x2F;show_bug.cgi?id=1301322&quot;&gt;this feature request&lt;&#x2F;a&gt; already exists for at least 10 years.
Let’s do it manually!&lt;&#x2F;p&gt;</description>
      </item>
      <item>
          <title>Part 2: From Docker Compose to Podman Quadlet: A Practical Guide Using Immich</title>
          <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
          <author>Unknown</author>
          <link>https://72p.de/posts/podlet/</link>
          <guid>https://72p.de/posts/podlet/</guid>
          <description xml:base="https://72p.de/posts/podlet/">&lt;p&gt;This is the second part on Podman.
In &lt;a href=&quot;https:&#x2F;&#x2F;72p.de&#x2F;posts&#x2F;nextcloud-quadlet&#x2F;&quot;&gt;my first post&lt;&#x2F;a&gt;, I described the basics of setting up Quadlets by hand.&lt;&#x2F;p&gt;
&lt;p&gt;In this follow-up I describe how to convert a conventional &lt;code&gt;docker-compose.yaml&lt;&#x2F;code&gt; file into a Quadlet setup by using &lt;a href=&quot;https:&#x2F;&#x2F;72p.de&#x2F;posts&#x2F;podlet&#x2F;immich.app&quot;&gt;Immich&lt;&#x2F;a&gt; as an example.&lt;&#x2F;p&gt;</description>
      </item>
      <item>
          <title>Part 1: Nextcloud Using Rootless Podman Quadlets</title>
          <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
          <author>Unknown</author>
          <link>https://72p.de/posts/nextcloud-quadlet/</link>
          <guid>https://72p.de/posts/nextcloud-quadlet/</guid>
          <description xml:base="https://72p.de/posts/nextcloud-quadlet/">&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;github.com&#x2F;containers&#x2F;podman&quot;&gt;



    




    
    
    
    



    

    
    
    
        
        

        
        
    
    &lt;img src=&quot;https:&amp;#x2F;&amp;#x2F;72p.de&amp;#x2F;posts&amp;#x2F;nextcloud-quadlet&amp;#x2F;logo-podman.svg&quot;
     width=&quot;auto&quot;
     height=&quot;auto&quot;
     alt=&quot;podman logo&quot;
     class=&quot;img-align-center&quot;
     style=&quot;height: auto; width: min(30.0%, 11.0em);  &quot;&gt;

&lt;&#x2F;a&gt;
When it comes to containers, it unfortunately has become common practice to run services with way more privileges than necessary (if not directly as root).
Docker remains the dominant player in this field but there is a new underdog and I think it’s better suited for most of the cases:
&lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Podman&quot;&gt;&lt;em&gt;Podman&lt;&#x2F;em&gt;&lt;&#x2F;a&gt; (short for pod manager) is a modern systemd-based substitute for &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Docker_(software)&quot;&gt;Docker&lt;&#x2F;a&gt; that already comes pre-installed with many operating systems – and it’s rootless by design.&lt;&#x2F;p&gt;
&lt;p&gt;Podman Quadlet is the analogue of Docker Compose – currently the de facto standard for deploying multi-container applications.
In the following, I describe my way to set up a Nextcloud instance using Podman Quadlets that runs exclusively with user privileges.&lt;&#x2F;p&gt;</description>
      </item>
    </channel>
</rss>
