Recent Blog Posts
Insights on AI Agents, Modern Web, and the Future of Engineering.
Rootless Docker Networking: Limitations and Workarounds
Without root, port forwarding, host networking, and driver support all change. The real limits of rootless container networking and the workarounds that hold up.
Docker and Your Firewall: iptables, nftables, and Docker Rules
Docker programs iptables and nftables itself. Learn what it writes, why editing its chains breaks networking, and how DOCKER-USER becomes your policy hook.
MTU Problems in Container Networks (and How to Fix Them)
Small pings work but big transfers hang. How to confirm an MTU black hole with do-not-fragment probing, where Docker sets MTU, and the fixes that hold up.
Overriding DNS Servers in Docker with `--dns`, `--dns-search`, and `--dns-option`
Override container resolvers with --dns, --dns-search, and --dns-option, plus daemon.json and Compose equivalents, and see how they interact with embedded DNS.
Inspecting Docker Network Configuration with `docker network inspect`
A field-by-field guide to reading docker network inspect output: IPAM subnets and gateways, per-container IPs and MACs, options, labels, and overlay peers.
Disconnecting Containers and Pruning Stale Docker Networks
Exit containers, disconnect them safely, and prune the stale Compose networks littering your host — with filters, labels, and a dry-run routine that won't delete live stacks.
Connecting One Container to Multiple Docker Networks
One container, several networks: connect running containers with docker network connect, repeat --network at run time, and scope aliases per network in Compose or the CLI.
Custom Subnets, IPAM, and Static Container IPs in Docker
Pin Docker subnets with --subnet, --gateway, and --ip-range, assign fixed container addresses with --ip, and control auto-allocation through default-address-pools.
Network Isolation with Docker Internal Networks
Create isolated Docker networks with --internal: no default route, no egress — but container-to-container traffic and embedded DNS still work. Proven with hands-on tests.
Choosing Between Macvlan and IPvlan
Macvlan gives every container its own MAC address; ipvlan shares the parent interface's MAC. Compare switch, cloud, and DHCP implications — and pick the right driver.
IPvlan L2 and L3 Modes for Container Addressing
Docker ipvlan shares the parent NIC's MAC address. Compare L2 (default) and L3 modes, plus L3s and the bridge/private/vepa flags, with a docker network create example for each.
Macvlan Modes Explained: Bridge, VEPA, Passthru, and Private
Docker's macvlan_mode option selects bridge, vepa, passthru, or private. How each mode moves frames at layer 2, when to pick it, and how to verify the mode a network is using.