Containers

Docker Rootless Mode — Secure Container Runtime for Homelabs

Complete guide to running Docker in rootless mode — no root daemon, no privileged containers. Covers installation, networking workarounds, Docker Compose, Proxmox LXC compatibility, and production readiness.

Docker Multi-Stage Builds — Practical Guide for Homelab

Master Docker multi-stage builds to shrink production images from 1.2GB to under 50MB. Covers Go, Python, and Node.js patterns with real Dockerfiles and build cache strategies.

Docker in Proxmox LXC — Performance Tuning and Production Guide

Run Docker containers inside Proxmox LXC with full performance. Covers nesting, overlay2 on ZFS, privileged vs unprivileged tradeoffs, cgroup resource limits, and security hardening for production homelab workloads.

Docker Container Security — Non-Root Users, Capabilities, and Runtime Hardening

Hardening Docker containers in your homelab isn’t optional — it’s how you prevent container escapes and privilege escalation. This guide covers non-root users, capability drops, read-only filesystems, and seccomp profiles with real Compose configs.

Grafana Alloy Log Collection — Docker Logs with Loki in 2026

Verify one Docker log stream end to end before expanding collection or replacing Promtail.

Docker Socket Proxy — Restrict API Access and Verify the Policy

Configure documented socket-proxy endpoint controls, keep the proxy private, and test permitted and denied requests.

Docker Compose Production Patterns for Homelabs — Healthchecks, Profiles, Secrets

Practical Docker Compose patterns for reliable homelab deployments. Healthchecks, conditional dependencies, profiles for optional services, secrets management, extension fields, and restart policies with real compose files.

Docker MACVLAN and IPVLAN — Giving Containers Real LAN IPs in Your Homelab

Step-by-step Docker MACVLAN and IPVLAN guide — give containers real LAN IPs for Pi-hole, Home Assistant, Scrypted. Host communication fix, Proxmox gotcha, multi-network Compose examples.

Docker Compose Patterns for Homelab Stacks

Use a small, complete stack to learn the deployment workflow. Then add only the networking, storage, and secret-handling features the application needs. Group services by ownership and lifecycle. A Compose project can contain several services, and you can operate on one service without restarting the whole project. Fixed container names are optional and can cause collisions or prevent scaling; service names are usually sufficient. Verification status Area Evidence and limits Technical review Official Docker documentation reviewed on October 31, 2026. Static checks Bash syntax and embedded Compose YAML checked. Runtime Docker unavailable in this review environment; no Compose CLI validation, image pull, HTTP request, or resource test executed. Example scope Disposable static HTTP lab on Linux, not a captured production stack. 1. Start with one complete project This demo uses BusyBox’s HTTP server and wget probe, a read-only content mount, loopback publishing, log rotation, and explicit resource limits. Use Bash and have curl installed on the host. ...

Proxmox LXC vs Docker — Picking the Right Container for Every Homelab Job

If you run Proxmox VE, you’ve got two container runtimes at your fingertips — LXC (built into Proxmox) and Docker (nested in an LXC or VM). Both are “containers” in the broad sense, but they solve different problems. Picking wrong means performance you don’t need or isolation you don’t have. This post walks through the decision criteria, backed by configs from an existing homelab running Proxmox 8.x with VLAN segmentation. ...