<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Selfhosting on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/selfhosting/</link>
    <description>Recent content in Selfhosting on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 29 Oct 2026 08:30:32 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/selfhosting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How I Got My Rootless Podman Home Assistant to Persist Across Reboots Without a Docker‑Compatible Registry</title>
      <link>https://linuxeries.org/post/2026-10-29-how-i-got-my-rootless-podman-home-assistant-t/</link>
      <pubDate>Thu, 29 Oct 2026 08:30:32 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-10-29-how-i-got-my-rootless-podman-home-assistant-t/</guid>
      <description>&lt;h2 id=&#34;persisting-a-rootless-podman-homeassistant-without-a-registry&#34;&gt;Persisting a Rootless Podman Home Assistant Without a Registry&lt;/h2&gt;&#xA;&lt;p&gt;Running Home Assistant in a rootless Podman container feels like a no‑frills, privilege‑minimal setup that sits comfortably in a homelab. The real pain point is making sure the image and its data stick around after a reboot when you don’t want to hit a Docker‑compatible registry. The trick is to treat a small part of the local filesystem as a “registry” and let Podman pull from it every time the system boots.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
