https://potterwhite.github.io/en/categories/docker/Recent content in Docker on Potter`s Log BookHugoenSat, 28 Mar 2026 00:00:00 +0000https://potterwhite.github.io/en/blog/2026/03/28/building-reproducible-docker-dev-environments-for-embedded-linux-rk3588-rv1126-rk3568/Sat, 28 Mar 2026 00:00:00 +0000https://potterwhite.github.io/en/blog/2026/03/28/building-reproducible-docker-dev-environments-for-embedded-linux-rk3588-rv1126-rk3568/<h1 id="building-reproducible-docker-dev-environments-for-embedded-linux">Building Reproducible Docker Dev Environments for Embedded Linux</h1> <h2 id="the-problem">The Problem</h2> <p>If you&rsquo;re working with embedded Linux boards — RK3588, RK3588S, RV1126, RK3568, or similar Rockchip SoCs — you know the pain:</p> <ul> <li>Every developer on the team has a slightly different toolchain version installed</li> <li>Build results differ between machines (&ldquo;it works on my Docker container&rdquo;)</li> <li>Supporting Ubuntu 20.04, 22.04, and 24.04 simultaneously without breaking any of them</li> <li>Ports collide when you run containers for multiple chip families at the same time</li> <li>Pushing images to a private Harbor registry requires glue scripts nobody documents</li> </ul> <p>The standard answer is &ldquo;containerise your dev environment&rdquo; — but the container definitions themselves become a maintenance burden. You end up with 5 Dockerfiles that diverge over time.</p>