How I Automated Multi-Platform Docker Image Builds for Embedded SoCs (RK3588, RV1126, RK3568)

How I Automated Multi-Platform Docker Image Builds for Embedded SoCs If you work with embedded Linux boards — RK3588, RV1126, RK3568, or similar ARM SoCs — you've probably hit these problems: Five different Dockerfiles, diverging more with every Ubuntu release Port collisions when running containers for multiple platforms at the same time Ubuntu 24.04 broke your apt mirror setup, pip installs, and UID assignments all at once Image push to Harbor requires glue scripts nobody maintains I spent months dealing with this and eventually built a tool called HarborPilot to solve it. Here's what I learned. The Core Problems Problem 1: Multiple Dockerfiles That Drift Apart When you start, one Dockerfile per platform seems fine. After 6 months, the RK3588 file has fixes that never made it to the RK3568 file, and Ubuntu 24.04 support requires changes that would break 20.04. Solution : One monolithic 5-stage Dockerfile. Platform-specific behaviour is injected via ARG / ENV at build time. Stage 1: b