3 ms·
Are you me? I just started a new job a few weeks ago, and guess what, I'm the first one (in my small group of ~5 or so) to have an M1. First it was just figuri
by pc86 5y ago
Are you me?
I just started a new job a few weeks ago, and guess what, I'm the first one (in my small group of ~5 or so) to have an M1. First it was just figuring out what the issue was, then trying UTM and manual port forwarding and getting horrible performance, then Colima which seems passable, but the default 2GB of RAM is useless for anything like kafka, so I end up having to allocate half the RAM of my machine just to docker containers.
- 411111111111111 5y agoI find it hilarious that you're both seemingly blame docker for these issues.
- pc86 5y agoI don't blame anyone for the issue. Well, maybe Apple itself but even then blame is pretty harsh. But from someone coming from 12+ years of software development on Windows, with occasional Mac usage personally, to suddenly doing development on a Mac, it was a big shock (mostly in a good way).
- zamalek 5y agoThe whole M1 thing is definitely Apple's fault, but it did lead me to a huge amount of bitrot in Docker tooling.
- vhanda 5y agoI'd recommend renting / buying a powerful (x64?) machine accessible over the internet. Ever since I did that docker on Mac became bearable. That coupled with vscode remote development even allows me to easily mount volumes. Plus I'm now less concerned about malicious 'npm post install scripts' which could potentially nuke all my data.
- zamalek 5y agoYou might also want to try Rancher Desktop. At the time I was solving things RD had some annoying bugs (so we are using colima for now), but it has come a long way and seems to handle networking a bit better than colima. I plan to post a blog about the whole lot. Shoot me an email, or a tweet, or something and I'll ping you when I get round to it.