https://www.pistack.xyz/tags/container-infrastructure/ Recent content in Container-Infrastructure on Pi Stack Hugo en-us Mon, 25 May 2026 00:00:00 +0000 https://www.pistack.xyz/posts/2026-05-25-self-hosted-container-image-inspection-dive-vs-skopeo-vs-crane-guide/ Mon, 25 May 2026 00:00:00 +0000 https://www.pistack.xyz/posts/2026-05-25-self-hosted-container-image-inspection-dive-vs-skopeo-vs-crane-guide/ <p>Container images are the fundamental building blocks of self-hosted infrastructure. Every Dockerfile produces an image composed of layered filesystems, metadata, and configuration. As teams build and maintain dozens or hundreds of container images, questions arise: How large is this image? Which layers consume the most space? Does this image contain the expected base layer? Can we verify the image signature before deploying it to production?</p> https://www.pistack.xyz/posts/2026-05-25-self-hosted-container-logging-drivers-journald-vs-fluentd-vs-syslog-vs-gelf-guide/ Mon, 25 May 2026 00:00:00 +0000 https://www.pistack.xyz/posts/2026-05-25-self-hosted-container-logging-drivers-journald-vs-fluentd-vs-syslog-vs-gelf-guide/ <p>Every Docker container generates stdout and stderr output — application logs, error traces, health check results, and debug information. By default, Docker stores these logs using the <code>json-file</code> driver, writing JSON-formatted entries to disk on the host. While this works for small deployments, production environments quickly outgrow this approach. Log files grow unbounded, querying requires parsing raw JSON, and there is no centralized view across multiple containers or hosts.</p>