Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Podman Desktop 1.2 Released: Compose and Kubernetes Support

podman-desktop.io

Post reply on HN
Print view View original

51–60 of 132 posts

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#51

Post by Art9681 »

chenster wrote: post #42

Do people still use Vagrant? Last time I tried Docker on Mac, it was painfully slow. So I kept using Vagrant, which used more disc space, but very fast, and the Intel Macbook pro fan never kicked in once like Docker did.

Containers on anything other than Linux run in a Virtual Machine. Depending on the platform, you may or may not have hardware acceleration. It's either using the software emulator (slow) or hardware acceleration. On the new M architecture, I believe Docker now supports Rosetta2 emulation via Apple's Hypervisor Framework so it is near native performance.

As far as Vagrant being faster than Docker, it's possible the qemu backend it uses was hardware accelerated and for whatever reason the Docker VM wasn't? Or perhaps you were using Docker Desktop which does take up a lot of compute capacity away? Try using the docker cli without docker desktop and see if it works better for you.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#52

Post by imiric »

I wish Podman wouldn't be a Docker replica, but a standalone product that competes in the container ecosystem with innovative features.

Initially the main advantage it had over Docker was rootless mode, but this has been available in Docker for a while now. What currently sets Podman (Desktop/Compose) apart from its Docker counterparts?

I've also run into issues running some containers with Podman that work fine with Docker. I still use it for some simple use cases, but I'm wondering more why bother with a copycat product that only plays catch-up to Docker, and has its own set of issues. And, incidentally, is run by Red Hat, and by extension IBM, which are increasingly hostile to OSS.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#53

Post by gnulinux »

foobarbecue wrote: post #46
pid-1 wrote: post #25

Earlier quoted context omitted.

I've been using Podman Desktop in Win11 for local development for about 6 months and I'd say nothing.

Nothing good? Nothing bad? I mean... if you're going to say nothing at all, no need to announce it...

As in nothing is missing to replace Docker Desktop.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#54

Post by sezycei »

foobarbecue wrote: post #46
pid-1 wrote: post #25

Earlier quoted context omitted.

I've been using Podman Desktop in Win11 for local development for about 6 months and I'd say nothing.

Nothing good? Nothing bad? I mean... if you're going to say nothing at all, no need to announce it...

The person you're responding to is responding to a comment asking what is missing from Podman Desktop it to replace Docker Desktop. It is missing nothing for them per their message.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#55

Post by Art9681 »

v3ss0n wrote: post #30
pid-1 wrote: post #24

Earlier quoted context omitted.

Fun fact: in Linux, Docker Desktop also uses a managed VM. https://docs.docker.com/desktop/faqs/linuxfaqs/#why-does-doc...

Yeah that's the worst thing docker did

If its hardware accelerated the performance difference would likely not matter. And you're not going to deploy a high performance container on a desktop environment since edit:[the desktop] will consume a much greater deal of resources from your host than the VM ever will. For deploying a development environment or self-hosted services it's fine.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#56

Post by hu3 »

imiric wrote: post #52

I wish Podman wouldn't be a Docker replica, but a standalone product that competes in the container ecosystem with innovative features. Initially the main advantage it had over Docker was rootless mode, but this has been available in Docker for a while now. What currently sets Podman (Desktop/Compose) apart from its Docker counterparts? I've also run into issues running some containers with Podman that work fine with…

Docker network effect is too important to ignore. That would be like swimming against the current.

For example, Deno (https://deno.land/) initially launched with precarious compatiliblity with Node.js, but eventually had to make compromises and adapt so Node.js projects could migrate easier.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#58

Post by Art9681 »

mogwire wrote: post #11
seaal wrote: post #4

Earlier quoted context omitted.

Yes. Perhaps OrbStack[1] is what you're looking for. [1] https://orbstack.dev/

Orbstack also uses a virtual machine. How does it work? Why is it fast? OrbStack uses a lightweight Linux virtual machine with tightly-integrated, purpose-built services and networking written in a mix of Swift, Go, Rust, and C. See Architecture for more details.

It's using Apple Virtualization Framework + Rosetta acceleration instead of third party hypervisor like QEMU. There are ways to do this via the CLI with a simple one line command if you have Xcode installed.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#59

Post by Art9681 »

bloopernova wrote: post #21
seaal wrote: post #4

Earlier quoted context omitted.

Yes. Perhaps OrbStack[1] is what you're looking for. [1] https://orbstack.dev/

Thank you for that link! 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.

Its using this:

https://developer.apple.com/documentation/virtualization

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#60

Post by Demiurge »

vbezhenar wrote: post #41
jadbox wrote: post #8

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 is extremely basic. Even on a single node Kubernetes is more capable than docker compose. Ingresses, Services, Deployments, Cronjobs, Statefulsets. Awesome operators. Cert-manager. There're so many things I could easily do with Kubernetes that would require countless unmaintainable bash scripts and ad-hoc approaches with docker-compose.

Yes, but 50% of the projects the parent poster sees, and 90% of the projects that I see, do not require any of that.
Post reply on HN