2 ms·
I actually meant that with vagrant, even us on Linux would run VMs, so if I set up a dev env, I can be pretty confident a colleague will run the same thing, wit
by e12e 7y ago
I actually meant that with vagrant, even us on Linux would run VMs, so if I set up a dev env, I can be pretty confident a colleague will run the same thing, with similar characteristics, on windows or Mac. With Docker, I feel it's still a bit kinda-sorta. Especially if you need to run multiple stacks for switching between projects.
- mixedCase 7y ago> With Docker, I feel it's still a bit kinda-sorta. What makes you think that? Only difference I can think of is use of hemorrhaging edge kernel primitives in your application. Even networking is handled by docker-compose and you don't have to worry about port collision.
- rumanator 7y ago> With Docker, I feel it's still a bit kinda-sorta. This was the first time I ever heard anything of the sort. Docker has been not only solid but by far the most performant system available, and running stuff on VMs always felt a half-baked solution in comparison. Can you shed some light on what led you to form your opinion?
- gmassman 7y agoA former colleague of mine used to rail on Docker for MacOS a few years ago. He always complained about it being super slow to sync with the local file system. I never had any issues but was running everything on Linux. Since then I've moved companies and now I'm running docker on a Mac. Haven't noticed any eggregious performance issues, but as I understand under the hood it's still basically running in a VM.