Using multi-arch Docker images to support apps on any architecture

As an aside, is this the new pipe curl to sudo bash?<p><pre><code> docker run --rm --privileged docker&#x2F;binfmt:66f9012c56a8316f9244ffd7622d7c21c1f6f28d</code></pre>

I&#x27;ve been leveraging docker buildx to create multi architecture images for a few months. It&#x27;s quite nice and simple, and I&#x27;ve been able to even automate the multiarch builds with GitHub Actions. See an example repo of mine here: <a href="https:&#x2F;&#x2F;github.com&#x2F;jmb12686&#x2F;docker-cadvisor" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;jmb12686&#x2F;docker-cadvisor</a>

I wish there was something like Bazel, Buck, Pants, or Please built on top of docker&#x2F;crio.<p>The docker build cache, and dockerizarion of tools, has made building, testing, and deploying software so much simpler. Unfortunately the next step in build systems (in my opinion) still has the mentality that people want to have mutable state on their host systems.<p>I hope someone extends BuildKit into a system like Bazel. All rules can be executed in containers, all software and deps can be managed in build contexts, you automatically get distributed test runners&#x2F;builds&#x2F;cache by talking to multiple docker daemons, etc.

The original purpose of most computer programmers was to write a program that would solve an immediate technical problem or a business requirement. The programmer was not concerned with the &quot;technical&quot; (though still important) question: What architecture is this CPU going to use? The first time a programmer encountered the question, his reaction was to try to compile a program that would run on the CPU.<p>I used to think of this process as a sort of reverse engineering exercise. To figure out what a CPU was doing, you needed to understand the architecture of the CPUs used by the people who were designing it. It was as though you were trying to reverse engineer a car engine using a hand-held computer; to understand how the engine worked you needed to understand how the car engine.

Interesting article but I can’t understand why cross compilation is dismissed.<p>It could have been improved by some performance benchmarks showing cross compilation performance in comparison with this emulation based solution. I find it hard to believe it makes sense to emulate when native performance is available.

I helped support the similar thing for Borg inside Google. It&#x27;s quite simple to support in a cluster manager, and highly powerful.

This looks interesting. I’ve been looking into getting Keybase running on a Raspberry Pi 4. This might help.

Anyone know how to get smaller docker images? I thought if I had all the previous layers in the docker registry that an upload would just be the size of the diff of the new layer, but this seems to <i>never</i> work.