71–80 of 231 posts
Perhaps a dumb question but I'm curious why people don't use a VPS or a cloud linux machine more for Docker/K8s development instead of running Docker locally on a Mac. In my experience Docker Desktop has been such a resource hog, and Apple's hypervisor implementation pretty poor. I much prefer to have all that heavy lifting isolated away from my development machine to keep it responsive and cool.
Perhaps a dumb question but I'm curious why people don't use a VPS or a cloud linux machine more for Docker/K8s development instead of running Docker locally on a Mac. In my experience Docker Desktop has been such a resource hog, and Apple's hypervisor implementation pretty poor. I much prefer to have all that heavy lifting isolated away from my development machine to keep it responsive and cool.
> In my experience Docker Desktop has been such a resource hog
Not sure if this is related to the specific project or what, but I haven't had tons of trouble with docker being a big hog.
That said, they are significantly changing the way Docker on M-Series CPUs works, working directly with Apple's Virtualization Framework which I believe improves performance.
Earlier quoted context omitted.
Docker obscures the implementation details. Part of this is by design: don't worry about the hard stuff, because Docker does it for you. It's completely unsurprising that many folks haven't spent the time to dive into the internals. In many cases, because they don't need to. Such is the nature of abstraction and higher level frameworks.
We aren't even close to a point where someone can just pretend a container is a magical box that just works. All abstraction leak. This is a relatively recent, quite leaky one.
I challenge this assertion. While it is of course true that there are situations that require a deeper knowledge of Docker, this is also not universally true.
Many projects these days have a Getting Started doc that has some options like:
- Build from source
- Install this package
- Use Docker
I often choose the Docker option because I know I'll (most likely) get a working version of the project in 5 minutes with minimal effort. I might not even fully understand the project yet or its architecture (much less that of Docker), but I can get it up and running with `docker pull` and `docker run`.
In many cases, I'll never need to know anything more.
I've personally spent more time using docker to build my own stuff, so I've had to learn more. But for many folks, it absolutely is a magical box that just works, and that's perfectly ok.
I agree that all abstractions tend to eventually leak. But depending on why you're using Docker, you may never have a reason to encounter that leakage.
Earlier quoted context omitted.
Lack of early availability? They sold $500 dev units specifically for this purpose.
They were not available for purchase by everyone.
Perhaps a dumb question but I'm curious why people don't use a VPS or a cloud linux machine more for Docker/K8s development instead of running Docker locally on a Mac. In my experience Docker Desktop has been such a resource hog, and Apple's hypervisor implementation pretty poor. I much prefer to have all that heavy lifting isolated away from my development machine to keep it responsive and cool.
If you have multiple developers working on the same product, you want each developer to have their own environment. In my experience, for cost, convenience, and productivity its made most sense to do this with local Docker. It also eliminates a lot of connectivity issues with running on a remote machine. > In my experience Docker Desktop has been such a resource hog Not sure if this is related to the specific project…
Earlier quoted context omitted.
Lack of early availability? They sold $500 dev units specifically for this purpose.
They were not available for purchase by everyone.
Earlier quoted context omitted.
If you have multiple developers working on the same product, you want each developer to have their own environment. In my experience, for cost, convenience, and productivity its made most sense to do this with local Docker. It also eliminates a lot of connectivity issues with running on a remote machine. > In my experience Docker Desktop has been such a resource hog Not sure if this is related to the specific project…
The main resource issue is because Docker runs in a VM, it can't share memory with the OS. So it's using the configured amount of memory (2GB by default) whether you're running busybox or an entire Kubernetes cluster.
Regardless, for me the cost of adding enough RAM to support Docker is less than the headache and expense of spinning up Docker images in the cloud.
Perhaps a dumb question but I'm curious why people don't use a VPS or a cloud linux machine more for Docker/K8s development instead of running Docker locally on a Mac. In my experience Docker Desktop has been such a resource hog, and Apple's hypervisor implementation pretty poor. I much prefer to have all that heavy lifting isolated away from my development machine to keep it responsive and cool.
cost? if im dropping $3k on a machine, I don't really wanna pay another $2k in cloud fees to do the dev work. you might say, "well get a cheaper computer!" but I find that cheaper computers have worse screens, battery life, and overall quality.
But I do agree with you. Cheaper laptops means a worse experience with almost everything.
Absolute disaster, this platform. The opacity and lack of early availability for development made for a really ugly adoption experience. I feel that people should not encourage this and vote with their money in the DevOps / Dev sector to discourage other companies from pulling the same stunt.
Lack of early availability? They sold $500 dev units specifically for this purpose.