3 ms·
I’ve worked in DevOps and companies I’ve worked for put the effort in when M1 came out, and now local images work fine. I honestly doubt it will have a huge imp
by anon7000 1y ago
I’ve worked in DevOps and companies I’ve worked for put the effort in when M1 came out, and now local images work fine. I honestly doubt it will have a huge impact. ARM instances on AWS, for example, are much cheaper, so there’s already lots of incentive to support ARM builds of images
- AnonymousPlanet 1y agoIt has a huge impact if you need to run the exact same container as in production. This kills Macs in those shops. And there are more than you might think.
- avhception 1y agoIn our small shop, I definitely made sure all of our containers supported aarch64 when die M1 hit the scene. I'm a Linux + Thinkpad guy myself, but now that I've got an x13s, even I am running the aarch64 versions!
- mxey 1y agoHow do you build multi-arch in CI? Do you cross-compile or do you have arm64 runners?
- spockz 1y agoIt depends. Mostly it is choosing the right base image architecture. For rust and golang we can trivially cross compile and just plunk the binary in the appropriate base image. For JVM based apps it is the same because we just need to have the jars in the right place. We can do this on either architecture. The only hold out is GraalVM which doesn’t trivially support cross compilation (yet).
- avhception 1y agoWe're mostly a PHP / JS (with a little Python on the side) shop, so for our own code it's mostly a matter of the right base image. Building our own images is done on an x86-64 machine, with the aarch64 side of things running via qemu.