3 ms·
Yeah that part was just "you're holding it wrong". I'm surprised that the option of running ARM containers on an ARM Linux isn't even mentioned? This would sure
by MrBuddyCasino 6y ago
Yeah that part was just "you're holding it wrong". I'm surprised that the option of running ARM containers on an ARM Linux isn't even mentioned? This would surely be the way forward?
- znpy 6y agoNot necessarily. What if your laptop is arm but your production environment is x86 ? You might think "well i'll have arm containers on my laptop and x86 containers in production" but then it means that dev and prod diverge: you're running different software, that might have different behaviors. One of the core ideas of docker was that you could have ideally the same artifact both in developmend, testing, staging, qa and prod environments. There's little way around the core problem: mac os x badly suited for running docker containers. The most performant way to run docker containers is to run them in native gnu/linux (hence: gnu/linux laptops)
- ed25519FUUU 6y agoCan you articulate any divergence you expect that wouldn’t otherwise be present running your container on another environment (prod)? I think “divergence” is a non-issue here if you’re testing locally, but the final build and push comes from another x86 CI host.
- MrBuddyCasino 6y ago> What if your laptop is arm but your production environment is x86 ? Thats what CI is for? > it means that dev and prod diverge It just means you're using a different architecture for your local development. Your DEV & TEST envs and your automated CI/CD runs can still use x86. Sure its a bit inconvenient, but for most types of development it won't matter much, as the stack doesn't compile to native anyway. I don't care if Java, JS or whatever runs on x86 or ARM.