11–20 of 124 posts
The whole point of docker was to have reproducible builds. What runs on the dev machine also runs on the server. But M1 macs change that in a major way. There might be bugs or available features in ARM versions of popular software, so what works on a dev machine might not work on the server and vice-versa.
Interestingly, the release version of Parallels for M1 Macs also dropped yesterday.
Is there a good way to spin up a Windows virtual machine with Docker on an Apple M1? I feel like the real solution I should be going with is Parallels or qemu. Just wanted to know if there was something I'm missing.
I wonder if the Apple Silicon decision is going to have a large impact on what CPUs are used in the datacenter? I (and I suspect many others) would just default to x86_64, because that's what I develop on and compile to. I suspect many developers on Apple computers will start to look at the differences and choose whatever meets their requirements while minimizing costs. Should this trend continue, this could even hav…
That moment is now here. Sure, it's only a subset of the market, but Mac devices are a significant percentage of developer computers (28%), way higher than in the general population (17%).
https://insights.stackoverflow.com/survey/2020#technology-de...
https://en.wikipedia.org/wiki/Usage_share_of_operating_syste...
I wonder if the Apple Silicon decision is going to have a large impact on what CPUs are used in the datacenter? I (and I suspect many others) would just default to x86_64, because that's what I develop on and compile to. I suspect many developers on Apple computers will start to look at the differences and choose whatever meets their requirements while minimizing costs. Should this trend continue, this could even hav…
Running docker containers on it was OK, and cross-compiling my golang monitoring stuff was easy enough.
But over time I just wanted to use my existing pipelines and deploy x86 stuff. So in the end it was a novelty, and while cheaper than an amd64 host it was eventually replaced so that I had a consistent set of deployment targets.
The whole point of docker was to have reproducible builds. What runs on the dev machine also runs on the server. But M1 macs change that in a major way. There might be bugs or available features in ARM versions of popular software, so what works on a dev machine might not work on the server and vice-versa.
The whole point of docker was to have reproducible builds. What runs on the dev machine also runs on the server. But M1 macs change that in a major way. There might be bugs or available features in ARM versions of popular software, so what works on a dev machine might not work on the server and vice-versa.
I didn’t realize this for a while myself, as the docker CLI tools are all free software. The “Desktop” variants are not, and embed spyware.
The whole point of docker was to have reproducible builds. What runs on the dev machine also runs on the server. But M1 macs change that in a major way. There might be bugs or available features in ARM versions of popular software, so what works on a dev machine might not work on the server and vice-versa.
What if your server is also running an ARM CPU though? For example with AWS Graviton