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

41–50 of 132 posts

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#41

Post by vbezhenar »

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.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#43

Post by foobarbecue »

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.

I don't think speed is a matter of your container engine (Docker vs Vagrant) but what virtual machine you are using. I usually use Docker without any virtualization since I'm running linux containers on linux. I'm guessing when you say Vagrant, your're probably using VMware or something. I don't know what Docker on mac might be using since I avoid using mac.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#44

Post by Cfu288 »

agumonkey wrote: post #34
flatline wrote: post #19

Earlier quoted context omitted.

Docker swarm is supposed to be the migration target for these cases, but I’ve never actually used it.

I lost track about it, I thought swarm was canceled

Docker swarm mode (still around) != docker swarm (cancelled). Poorly named so the confusion is normal

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#45

Post by preya2k »

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.

For me, I really enjoy how basic it is. I’ve never missed any of these things for my simple single-host scenarios.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#46

Post by foobarbecue »

pid-1 wrote: post #25
joaoqalves wrote: post #5

What's missing to fully replace Docker Desktop?

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...

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#47

Post by chenster »

foobarbecue wrote: post #43
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.

I don't think speed is a matter of your container engine (Docker vs Vagrant) but what virtual machine you are using. I usually use Docker without any virtualization since I'm running linux containers on linux. I'm guessing when you say Vagrant, your're probably using VMware or something. I don't know what Docker on mac might be using since I avoid using mac.

I guess when I mentioned slow, it uses lots of resources on parent OS. Yes, it's Virtual Box I believe.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#48

Post by tecleandor »

0xbadcafebee wrote: post #35

Why does Compose still only work on one server? I am perpetually perplexed that nobody has patched Compose to manage k8s resources, have its own multi-node support, or push Swarm more. How has nobody fixed this? The tool is 9 years old.

Well there are two things:

Compose, "the binary" [1]. It used to be "just" a Python helper script that called Docker, used to deploy multiple containers in a common network easily. It was rewrited in Go, and now it's kind of a plugin for Docker. I think it's strongly tied to Docker primitives, and wouldn't be that easy to modify it to work on different container orchestrators.

But there's also Compose "the file format" [2]. There are tools, like Kompose[3], that understand the Compose format, and can use it to deploy in Kubernetes.

  1: https://github.com/docker/compose
  2: https://compose-spec.io/
  3: https://kompose.io/

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#49

Post by [deleted] »

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.

[deleted]

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#50

Post by freeplay »

throwaway106382 wrote: post #37

Is there a way to make Podman Desktop use the default system connection rather than the default podman machine? When I do `podman ps` my client connects to my development VM that is not managed by podman, but I can't seem to find a way to make Podman Desktop do that.

podman system connection

That command will let you manage what instance the podman cli is connecting to

https://docs.podman.io/en/latest/markdown/podman-system-conn...

Post reply on HN