<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nas on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/nas/</link>
    <description>Recent content in Nas on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 15 Oct 2026 09:09:02 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/nas/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Preventing Disk Space Woes on a Home NAS by Configuring Logrotate for Docker Container Logs</title>
      <link>https://linuxeries.org/post/2026-10-15-preventing-disk-space-woes-on-a-home-nas-by-c/</link>
      <pubDate>Thu, 15 Oct 2026 09:09:02 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-10-15-preventing-disk-space-woes-on-a-home-nas-by-c/</guid>
      <description>&lt;h2 id=&#34;why-docker-logs-can-eat-a-nas&#34;&gt;Why Docker logs can eat a NAS&lt;/h2&gt;&#xA;&lt;p&gt;A home NAS is usually a single‑disk or a small RAID array.&lt;br&gt;&#xA;When you run several containers—media servers, databases, CI runners—each one writes a JSON log file under&#xA;&lt;code&gt;/var/lib/docker/containers/&amp;lt;id&amp;gt;/&amp;lt;id&amp;gt;-json.log&lt;/code&gt;.&lt;br&gt;&#xA;If you leave the default &lt;code&gt;json-file&lt;/code&gt; driver untouched, those files grow indefinitely.&lt;br&gt;&#xA;On a 1 TB NAS, a handful of containers can fill the drive in weeks, forcing you to delete data or upgrade hardware.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
