<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Sqlite on Jakub Žilínek</title>
    <link>https://zilinek.cloud/tags/sqlite/</link>
    <description>Recent content in Sqlite on Jakub Žilínek</description>
    <generator>Hugo -- 0.145.0</generator>
    <language>en</language>
    <lastBuildDate>Sun, 16 Mar 2025 12:30:00 +0000</lastBuildDate>
    <atom:link href="https://zilinek.cloud/tags/sqlite/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Homelab - How I managed to kill my K3S with SQLite</title>
      <link>https://zilinek.cloud/posts/sqlite-issue/</link>
      <pubDate>Sun, 16 Mar 2025 12:30:00 +0000</pubDate>
      <guid>https://zilinek.cloud/posts/sqlite-issue/</guid>
      <description>&lt;h1 id=&#34;how-it-started&#34;&gt;How it started&lt;/h1&gt;
&lt;p&gt;One day I have tried to use my plex instance and it was unreachable. I started digging into it.&lt;/p&gt;
&lt;p&gt;There were couple of containers that wouldn&amp;rsquo;t start and also inspection using &lt;code&gt;k9s&lt;/code&gt; CLI was taking ages.&lt;/p&gt;
&lt;h2 id=&#34;started-digging&#34;&gt;Started digging&lt;/h2&gt;
&lt;p&gt;I have started looking into logs, I saw couple of issues related to SQL - like &lt;code&gt;slow queries&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Then I remembered that K3S is using SQLite as default database, which may not be ideal, for long living clusters.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
