3 ms·

I guess the flip side is that, hopefully, the Docker ecosystem will start getting a lot better at multi-arch, at least for x86-64 and ARM. I just ordered an M1

I guess the flip side is that, hopefully, the Docker ecosystem will start getting a lot better at multi-arch, at least for x86-64 and ARM. I just ordered an M1 MBP and I'll be quite happy to start thwacking bugs in images and upstreaming the fixes.

nomel 6y ago
I naively assumed, until today, that the whole point of using linux in docker was that you get the multi-arch goodness of linux for free!
- Polylactic_acid 6y ago
  Not at all. Docker on a raspberry pi is a massive pain in the ass. Half the images are not compiled for ARM.
  - vocram 6y ago
    Not a bit deal. Building ARM images from Dockerfiles is trivial. And it has the benefit of not having to trust an upstream image content. If you want to go the extra mile, contribute to the project to provide multi arch images support.
- caymanjim 6y ago
  What multi-arch goodness of Linux? Linux can't magically run code from any architecture even without Docker in the mix, and unless someone is maintaining packages for your specific architecture, you're building them yourself.
  - unethical_ban 6y ago
    As a non-processor geek, isn't M1 an arm chip? How long will it take arbitrary software to target it?
    - neurostimulant 6y ago
      Yes but afaik most arm softwares target arm7, not aarch64.
Fumtumi 6y ago
We operate a k8s cluster with our own software and lots of opensource stuff. If i can't run our own images on a future mac, i will no longer buy one. I can't force my team to maintain two versions if there is no better business reason. I'm quite curious how this will play out.
rubyn00bie 6y ago
Just a heads up; I haven't tried using my DTK in a while but... development was still VERY rough last time I checked. I was pretty much forced to write code on an x86 machine and schlep it over via ssh to then run it. Also, be real careful you don't accidentally build for x86 when installing libraries or it all goes to shit. I got bitten by this by using iTerm (building it from source was fine though) and not realizing it was the x86 variant. That is to say, make sure your terminal is the system terminal or built for ARM-- otherwise when you install things using package managers they'll be the x86 variant. Like, I'm super stoked for the M1, but also just totally fucking irritated about the toolchain changes and MacOS in general... They've not been the best stewards of their software and developer communities as of late, and they're pushing a totally proprietary architecture onto them expecting them to foot the bill (hours spent fixing/debugging) to make their platform usable. Truly, I get paid to write software that runs on Linux not on Macs. In fact, I've never gotten paid to write software for Macs, because no production systems use Macs. Now it is harder for me to do primary development on a Mac; because I must fix MacOS or live with MacOS only bugs... bugs which only exist on a platform I do not intend to deploy my code to... these aren't just some config bugs either they're going to be a fucking mess of irritating, show-stopping, moving targets with a negative ROI. I still can't believe they didn't incorporate containers into the OS before switching platforms to keep developers around but that's a totally different rant.

nomel 6y ago

I naively assumed, until today, that the whole point of using linux in docker was that you get the multi-arch goodness of linux for free!

Polylactic_acid 6y ago
Not at all. Docker on a raspberry pi is a massive pain in the ass. Half the images are not compiled for ARM.
- vocram 6y ago
  Not a bit deal. Building ARM images from Dockerfiles is trivial. And it has the benefit of not having to trust an upstream image content. If you want to go the extra mile, contribute to the project to provide multi arch images support.
caymanjim 6y ago
What multi-arch goodness of Linux? Linux can't magically run code from any architecture even without Docker in the mix, and unless someone is maintaining packages for your specific architecture, you're building them yourself.
- unethical_ban 6y ago
  As a non-processor geek, isn't M1 an arm chip? How long will it take arbitrary software to target it?
  - neurostimulant 6y ago
    Yes but afaik most arm softwares target arm7, not aarch64.

Fumtumi 6y ago

We operate a k8s cluster with our own software and lots of opensource stuff. If i can't run our own images on a future mac, i will no longer buy one. I can't force my team to maintain two versions if there is no better business reason. I'm quite curious how this will play out.

rubyn00bie 6y ago

Just a heads up; I haven't tried using my DTK in a while but... development was still VERY rough last time I checked. I was pretty much forced to write code on an x86 machine and schlep it over via ssh to then run it. Also, be real careful you don't accidentally build for x86 when installing libraries or it all goes to shit. I got bitten by this by using iTerm (building it from source was fine though) and not realizing it was the x86 variant. That is to say, make sure your terminal is the system terminal or built for ARM-- otherwise when you install things using package managers they'll be the x86 variant. Like, I'm super stoked for the M1, but also just totally fucking irritated about the toolchain changes and MacOS in general... They've not been the best stewards of their software and developer communities as of late, and they're pushing a totally proprietary architecture onto them expecting them to foot the bill (hours spent fixing/debugging) to make their platform usable. Truly, I get paid to write software that runs on Linux not on Macs. In fact, I've never gotten paid to write software for Macs, because no production systems use Macs. Now it is harder for me to do primary development on a Mac; because I must fix MacOS or live with MacOS only bugs... bugs which only exist on a platform I do not intend to deploy my code to... these aren't just some config bugs either they're going to be a fucking mess of irritating, show-stopping, moving targets with a negative ROI. I still can't believe they didn't incorporate containers into the OS before switching platforms to keep developers around but that's a totally different rant.