docker on Alex King's blog

Docker Bridging to Host Network

Tue, 11 Nov 2025 00:00:00 +0000

This article is translated from Chinese to English by ChatGPT. There might be errors.

The subtitle of this post could be “My Hacky Docker Networking Setup”. It mainly describes the pitfalls I ran into when configuring Docker to bridge to the host network.

Docker’s bridge network is an internal network; all communication with the outside world has to go through L3 routing and NAT, which is inconvenient for some applications. If you want to bridge to the host network, the simplest approach is to use macvlan. However, macvlan has the drawback that it cannot communicate with the host, so it’s not a perfect solution.

Dockerfile Pitfalls

Mon, 07 Mar 2022 00:00:00 +0000

This article is translated from Chinese to English by ChatGPT. There might be errors.

Recently I’ve been writing Dockerfiles at work to build an image that contains a conda environment. I ran into countless pitfalls and can only lament my lack of skill; I’m recording them here.

Enable TLS Connection for Docker Daemon

Thu, 10 Feb 2022 00:00:00 +0000

This article is translated from Chinese to English by ChatGPT. There might be errors.

Background: The NAS uses a Xeon W-2140B CPU without an integrated GPU, and the onboard ASPEED graphics is essentially unusable for hardware acceleration, so Jellyfin cannot use hardware decoding. Although I tested that CPU software decoding can handle one 4K-to-4K transcoding stream smoothly, the CPU usage is already close to 100%. So I decided to move Jellyfin to an Ubuntu VM running on ESXi with a Core i3 8100T. To conveniently manage Docker on both machines, I want the Portainer instance running on the NAS to connect to the new Docker Daemon.

A Docker DNS Troubleshooting Story

Tue, 04 Feb 2020 00:00:00 +0000

This article is translated from Chinese to English by ChatGPT. There might be errors.

This afternoon a colleague came to me with a problem: a container couldn’t resolve domain names. I thought DNS issues wouldn’t be hard to fix… and then spent the next 8 hours troubleshooting.