Network Services
Network Binding and Configuration
Section titled “Network Binding and Configuration”The DNSmasq service binds to a specific network interface and IP address that are only known at runtime . The Helm Deployment passes every dnsmasq argument to the container, allowing the LAN interface and IP to be configured dynamically rather than being hardcoded in the image . This design supports the isolated 10.88.0.0/24 LAN environment required for PXE-booting .
Process Management
Section titled “Process Management”The container uses tini as the entrypoint to manage the dnsmasq process [src: containers/gb10-dnsmasq/Dockerfile:L19]. tini is responsible for reaping the dnsmasq child process, which ensures the pod terminates cleanly when it receives a SIGTERM signal . The iproute2 package is also installed in the image, providing a full /sbin/ip utility [src: containers/gb10-dnsmasq/Dockerfile:L18]. This is necessary because the gb10-provision.lanInit initContainer reuses this image and requires ip addr replace, which is not available in Alpine’s busybox .
