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

81–90 of 132 posts

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#81

Post by vbezhenar »

justin_oaks wrote: post #72
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…

> Simple setups will be as simple with Kubernetes. That is true if you already have Kubernetes. If you don't, then you still need to run and configure the Kubernetes' control plane (e.g. kube-apiserver, etcd, scheduler, etc). Doing that alone may exceed the complexity of a simple setup. I say this as someone who has looked at Kubernetes a lot and wanted to use it, but could never justify it. I have concluded multiple…

kubeadm init is all you need to run and configure everything. It's installed via dep/rpm.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#82

Post by whoknowswhat11 »

constantly wrote: post #74
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…

How many lines of unnecessary code have been written to be “ready to scale” and that never happens? This is an anti pattern and I would caution anyone from falling into this mindset where they feel they need Kubernetes even for simple things. I urge people to start simple, focus on features, and deal with complexity when the need actually arises. This Cult of Kubernetes has to go.

I'm just using docker alone sometimes w some AWS service set - agreed completely. So simple to iterate, test and deploy. The performance and even reliability of stuff now is impressive. One AMD 7950x3d box on a 5 gig att fiber connection. Price / perf / simplicity is amazing

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#83

Post by eriksjolund »

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…

Podman can run a socket-activated network server (such as docker.io/library/nginx) with the "--network=none" option. This improves security.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#84

Post by rzmmm »

badrequest wrote: post #76
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.

I've never understood using K8s in local dev over docker-compose, but I can absolutely see why someone would use it production.

If someone is working on complex kubernetes configuration, it's beneficial to have kubernetes in local dev environment, since it's trivial to test changes.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#85

Post by justin_oaks »

v3ss0n wrote: post #31
joaoqalves wrote: post #5

What's missing to fully replace Docker Desktop?

Lazydocker is all you need to replace docker desktop

When I was running Docker Desktop on Windows, I never used the GUI. Instead I always ran commands (docker or docker-compose) on the command line. In that case, the major benefit to Docker Desktop was having it set up the Linux VM that you run Docker on. That is a huge benefit.

Lazydocker is awesome, though. Thanks for introducing it to me. I just installed it and I'm loving it. I've used Portainer in the past, but didn't like it enough to leave it running continuously.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#86

Post by bloopernova »

Art9681 wrote: post #59
bloopernova wrote: post #21

Earlier quoted context omitted.

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

Interesting, I thought Docker Desktop was doing that too. When I have time (HA!) I will try to compare podman/orb/docker a bit more.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#87

Post by c-hendricks »

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.

> Docker compose is extremely basic

Yup thanks for noticing, that's why I use it

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#88

Post by totallywrong »

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 still requires a daemon, even in rootless mode. Podman does not.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#89

Post by mfer »

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

It sorta makes sense for a bunch of reasons:

1. You only have to deal with one Linux distro in the VM. Managing things across many distros can be difficult at that level.

2. There are times you want to blow away your environment. Can't do this if things running on the host.

3. You'll want to controll the resources your workloads uses so they don't make the Linux desktop unresponsive. VMs provide that level of separation.

I could go on but you get the point. If you're a power user who wants it on the host you can do that. For the masses of this kind of product, a VM has a lot of advantages.

Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support

#90

Post by hu3 »

mattrick wrote: post #68
hu3 wrote: post #62

Earlier quoted context omitted.

Just a nit. Docker on Windows is near native-like performance, using WSL2. WSL2 even supports running Linux GUI applications and GPU passthrough.

WSL2 still runs in a VM so it has the performance implications of that, not that they usually end up being that significant (I have found that memory usage in WSL2 is usually ridiculously high, though). I think the support for Linux GUI applications is achieved by running an X server on the Windows side of things.

Funny thing is that most of my stuff runs faster in WSL2 than Windows because it bypasses Windows built-in virus scanner.
Post reply on HN