3 ms·
1. Run arm-based debian using Parallels, headless using `prlctl`. SSH in and use tmux. 2. Everything you install will be arm based. Docker will pull arm-base
by tonyhb 4y ago
1. Run arm-based debian using Parallels, headless using `prlctl`. SSH in and use tmux.
2. Everything you install will be arm based. Docker will pull arm-based images locally. Most every project (that we use) now has arm support via docker manifests.
3. Use binfmt to cross-compile x86 images within prlctl, or have CI auto-build images on x86 machines.
That pretty much does it.
- aidos 4y agoYup. We have a lot of complex dependencies so a couple of us got M1s so we could charge into it headfirst to get it sorted. It wasn’t too bad. We had a couple of 3rd party things stuck on x86 so we emulated them on qemu within the vm. Slow, but ok (eventually we replaced them). We were using UTM but have recently switched to Parallels, which is nice. Our prod stayed on x86 but we’ve started moving to graviton3 which is better bang for buck. Suspect it’ll end up being a common story for others too. m1s are just such nice machines that I’d go quite out of my way to stay on them now.
- nonethewiser 4y agoHow would you handle docker images in a team where some use M1 and others use intel?
- pmontra 4y agoA customer of mine has two different Dockerfiles, one for Intel and one for M1. Deploys are Intel and are built on a CI server. No image gets out of our laptops.
- password4321 4y agoA couple more votes for this over the past year, using NixOS: https://news.ycombinator.com/item?id=31094361&p=2#31101729 https://news.ycombinator.com/item?id=31094361&p=2#31101729 https://news.ycombinator.com/item?id=31094361#31098721 https://news.ycombinator.com/item?id=31094361#31098721 https://news.ycombinator.com/item?id=27825240#27825420 https://news.ycombinator.com/item?id=27825240#27825420