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

101–110 of 132 posts

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#101

Post by ducharmdev »

At work I was initially using podman on an M1 MacBook, but switched to Rancher Desktop + dockerd a couple months ago after having too many issues with podman. Many in my org are also moving away from podman for similar reasons.

I could never get bind mounts working consistently, relying instead on volumes, which are more awkward/less explicit when persisting local DBs used when testing.

I've had zero problems with Rancher Desktop + dockerd - definitely recommend it for M1 users that are having issues with podman.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#102

Post by geerlingguy »

gtirloni wrote: post #96
vbezhenar wrote: post #63

Earlier quoted context omitted.

Simple setups will be as simple with Kubernetes. However with Kubernetes your infrastructure will be ready to scale. You need to expose both front-end and back-end services under the same host? No need to tinker with nginx configs, you just create two ingresses and do it in a standardized way. You need to run your service with two replicas and rolling zero-downtime update? Kubernetes has it out of the box. Good luck…

> However with Kubernetes your infrastructure will be ready to scale. 90% of the projects won't need scale. You're paying forward for something you won't use most of the time. Speaking as a k8s admin.

Premature optimization is the root of all evil.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#103

Post by kbenson »

ducharmdev wrote: post #101

At work I was initially using podman on an M1 MacBook, but switched to Rancher Desktop + dockerd a couple months ago after having too many issues with podman. Many in my org are also moving away from podman for similar reasons. I could never get bind mounts working consistently, relying instead on volumes, which are more awkward/less explicit when persisting local DBs used when testing. I've had zero problems with Ra…

> I could never get bind mounts working consistently

What type of problems were you seeing? Was it with podman or through podman desktop, and possibly some issue with what it was attempting?

bind mounts are a pretty standard kernel feature, so I'm wondering how podman/podman desktop could have been screwing it up, unless it was some user level permissions thing.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#104

Post by ragnese »

hu3 wrote: post #56
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.

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

And we have yet to see if that ends up being the right call. These things are always really tough. On the one hand, compatibility with existing stuff makes migration easier, but then if it's not actually different enough, we have no reason to change to the new thing.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#105

Post by ducharmdev »

nightowl_games wrote: post #91

To all the people pointing out that docker compose doesn't scale, I use docker compose locally in a vs code dev container and then k8s on production. Running k8s locally seems too complex, maybe it's not so bad but I'm happy with using docker compose dev container for development

To me, docker compose is simply a more readable way of running docker commands; anything you can do with the docker cli, you can run as a docker compose file.

Just like how a shell script is easier to manage than stringing lots of commands in the terminal, defining services in yaml is easier to manage than adding a million flags to your docker commands.

Of course at a certain point you may need further abstractions, but I agree with you that these should only be used if they're actually needed.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#106

Post by ducharmdev »

mfer wrote: post #20
joaoqalves wrote: post #5

What's missing to fully replace Docker Desktop?

That depends on what you need. For most people and use cases you can replace it with something like Rancher Desktop [1]. But, there are use cases and situations where you needed Docker Desktop. Disclaimer, I started Rancher Desktop. [1] https://rancherdesktop.io/

I switched from podman to Rancher Desktop at work recently, and it's been a very smooth experience - thank you for your work!

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#107

Post by MuffinFlavored »

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.

> Awesome operators

https://github.com/operator-framework/awesome-operators archived since 2021 and now https://operatorhub.io/

I hadn't heard of this, interesting. Layers and layers of abstractions. What an interesting way to solve things. "It's YAML all the way down"?

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#108

Post by llama052 »

MuffinFlavored wrote: post #107
vbezhenar wrote: post #41

Earlier quoted context omitted.

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.

> Awesome operators https://github.com/operator-framework/awesome-operators archived since 2021 and now https://operatorhub.io/ I hadn't heard of this, interesting. Layers and layers of abstractions. What an interesting way to solve things. "It's YAML all the way down"?

If you can grasp the layers of abstraction it's a really really fast way to ship operational solutions. Yaml aside it's great for smaller teams and empowers them to do a lot more than they could traditionally do.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#109

Post by llama052 »

belthesar wrote: post #40
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've done some labbing with Swarm. Swarm is _just different enough_ to be a pain, but just similar enough to fool you into thinking you know what you're doing. Because swarm was also confused terminology (at one point there were two things with the name swarm that did things differently) the tech definitely got a bad rap for a while, but it also stagnated supporting tooling. You can use things like Portainer and Swar…

Honestly with a github action and Argo CD workflow the kubernetes patterns aren't that scary. However maybe I'm just too comfortable in the ecosystem at this point.

I will say Kubernetes being as open as it is and all the overlapping tooling would seem incredibly overwhelming for someone trying to enter that space.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#110

Post by foobarbecue »

sezycei wrote: post #54
foobarbecue wrote: post #46

Earlier quoted context omitted.

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.

ooo thanks
Post reply on HN