<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fluentd on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/fluentd/</link>
    <description>Recent content in Fluentd on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/fluentd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Container Log Driver Comparison: Docker Logging Backends for Production</title>
      <link>https://www.pistack.xyz/posts/2026-06-01-self-hosted-container-log-drivers-docker-guide/</link>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-01-self-hosted-container-log-drivers-docker-guide/</guid>
      <description>&lt;p&gt;Every container produces logs — but where those logs go depends entirely on your Docker logging driver configuration. The default &lt;code&gt;json-file&lt;/code&gt; driver stores logs locally on disk, which works for development but quickly becomes a liability in production. Rotated logs fill your disk, critical errors go unnoticed, and debugging across multiple containers requires SSH access to every host.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
