5 ms·
Is it going to be interesting to see how new Apple machines running ARM based processors plays out. Writing code, and building docker images locally on ARM and
by willejs 6y ago
Is it going to be interesting to see how new Apple machines running ARM based processors plays out.
Writing code, and building docker images locally on ARM and building and running the same code on X86 in production could potentially, in some circumstances cause some issues. If not, it's a bit of a pain to potentially build and publish x86 and ARM images so that people can run them anywhere (Some projects are already doing this). Running production on ARM could work if you wanted to, but right now the instance types are very restricted in terms of different combinations of cpu/disk/io.
- shams93 6y agoI wonder if this will drive z move to deploy on arm based cloud instances like aws has arm based vms for ec2
- pmart123 6y agoIt seems like it very well could. It probably won't be power users, but perhaps, it is the start of more arm based deployments.
- umvi 6y ago> building docker images locally on ARM and running it on X86 in production could potentially, in some circumstances cause some issues. Won't it always cause issues? If you build locally you are packaging ARM binaries in zfs which won't run on x86... unless you somehow signal to docker that you want a different arch when building
- outworlder 6y ago"Somehow". That's exactly what you have to do. Build multi-arch containers with docker buildx.
- kall 6y agoI assume (but don‘t know) that most workflows build the deployed docker image in some kind of CI service. Is that not true?
- willejs 6y agoSorry I made an edit to clarify what I meant as it was confusing.
- happosai 6y agoIf you are developing on Apple silicon, the path of least resistance is to deploy to AWS Graviton2 instances, even if the instance cpu/memory/io combination isn't perfect fit for your usecase.
- willejs 6y agoI agree. However for a lot of people, their workloads have been running on x86 forever, maybe their production instances are not reproducible, and with combinations of cpu/memory/io being limited, at scale this could cost $$$. I’m just curious to see how this will pan out.