21–30 of 132 posts
Forgive my naïveté regarding Podman. On macOS, does this use the same virtualization approach that docker desktop uses?
Yes. Perhaps OrbStack[1] is what you're looking for. [1] https://orbstack.dev/
It's a very interesting product, it does use a VM, but seems to have some "special sauce" code to improve the speed of things. It also says it shares the kernel among multiple VMs. Very cool stuff.
Forgive my naïveté regarding Podman. On macOS, does this use the same virtualization approach that docker desktop uses?
For simplicity, the tooling often tries to make this simple and transparent to use.
I'm very happy to see you better support for docker compose. I think about 50% of the time I find Kubernetes used in production/development when it could have just used Compose along with a simple Terraform or Pulumi deploy script.
ah the 1% of the time you do want to use something in kubernetes and you have a pile of compose is pretty demoralising though
Forgive my naïveté regarding Podman. On macOS, does this use the same virtualization approach that docker desktop uses?
To run Linux containers you will always need Linux somewhere. On macOS this would be in a VM that's usually managed by the tooling. Docker Desktop, Rancher Desktop, lima, and others all do this. On Windows you have the Windows Subsystem for Linux v2 that uses a VM. For simplicity, the tooling often tries to make this simple and transparent to use.
https://docs.docker.com/desktop/faqs/linuxfaqs/#why-does-doc...
What's missing to fully replace Docker Desktop?
Earlier quoted context omitted.
I guess they stopped doing this and now consider the product mature from looking at their website, but Docker Compose used to tell you that it wasn't suitable or intended for production use. That seemed like a pretty good reason not to do it.
Compose has its own footguns, but I've run a number of services with just Compose on a VM or direct on bare metal and the few little issues I've had were easy to debug and fix. Very much unlike Kubernetes, where even a small deployment can sometimes be maddening to debug. Great for larger deployments where complexity is basically guaranteed, but anything that could run on one server with a hot spare is a great fit fo…
I'm very happy to see you better support for docker compose. I think about 50% of the time I find Kubernetes used in production/development when it could have just used Compose along with a simple Terraform or Pulumi deploy script.
Docker compose falls apart when you need something clustered across nodes or any other multi-host deployment. Once you have to rip it apart it becomes way less appealing. Though I haven't tried it in a while and perhaps the ergonomics have changed.
The A and B group can be implemented with docker compose and deployed to each cluster with pulumi/Terraform. Two or a hundred, it doesn't really matter how many cluster groupings you have.
Earlier quoted context omitted.
Docker compose falls apart when you need something clustered across nodes or any other multi-host deployment. Once you have to rip it apart it becomes way less appealing. Though I haven't tried it in a while and perhaps the ergonomics have changed.
Docker swarm is supposed to be the migration target for these cases, but I’ve never actually used it.
Earlier quoted context omitted.
To run Linux containers you will always need Linux somewhere. On macOS this would be in a VM that's usually managed by the tooling. Docker Desktop, Rancher Desktop, lima, and others all do this. On Windows you have the Windows Subsystem for Linux v2 that uses a VM. For simplicity, the tooling often tries to make this simple and transparent to use.
Fun fact: in Linux, Docker Desktop also uses a managed VM. https://docs.docker.com/desktop/faqs/linuxfaqs/#why-does-doc...
Earlier quoted context omitted.
To run Linux containers you will always need Linux somewhere. On macOS this would be in a VM that's usually managed by the tooling. Docker Desktop, Rancher Desktop, lima, and others all do this. On Windows you have the Windows Subsystem for Linux v2 that uses a VM. For simplicity, the tooling often tries to make this simple and transparent to use.
Fun fact: in Linux, Docker Desktop also uses a managed VM. https://docs.docker.com/desktop/faqs/linuxfaqs/#why-does-doc...