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
Podman Desktop 1.2 Released: Compose and Kubernetes Support
91–100 of 132 posts
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#92Earlier 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.
WSL2 uses a Hyper-V virtual machine [1], which is a native hypervisor [2] and doesn't come with most of the performance costs of software VMs.
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#93I 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…
> but a standalone product that competes in the container ecosystem with innovative features.
It has tons of features, but people don't pay attention to them due to the Docker being the lowest common denominator.
For example, there is absolutely no need for Compose. You create a pod and all the containers in it. You can then ask podman to generate all the systemd units for it.
I am also very worried about the IBM issue though, I wonder how long it will be until they slay this golden goose.
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#94I 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…
Big thing for me is Podman being daemon-less, making it a lot easier to integrate with existing tools since you don't have to treat it as it's own thing. It's already had easy systemd integration for a while now[0] and with Quadlet[1] I don't even bother writing compose files anymore; I just add a [Container] or [Volume] section to the same unit file templates I use everywhere else and it's all taken care of. Though to be honest, I mostly used bash script over compose files anyway since podman-compose never really worked as well.
Someone else has already mentioned built in pod support, plus you can generate kube files from existing pods for easy deployment.
So you end up with this nice progression of managing:
1. one-off/short term containers with podman run
2. longer running containers with podman generated systemd units
3. generation deployment of above long running containers with Quadlet
4. pods and more complicated setups on one machine with kube files
5. pods and more complicated setups across multiple machines with kubernetes
Which is a really nice stack to work with since they all use the same toolbox.
And that's outside of other small features like not having to worry about the docker package updating restarting the daemon and taking it all down, socket activation (through systemd units), and auto-updates.
[0] https://docs.podman.io/en/latest/markdown/podman-generate-sy... [1] https://docs.podman.io/en/latest/markdown/podman-systemd.uni...
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#95I'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
#96Earlier quoted context omitted.
For me, I really enjoy how basic it is. I’ve never missed any of these things for my simple single-host scenarios.
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.
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#97Earlier quoted context omitted.
> 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.
I almost spilled my coffee, seriously.
I hope you're not putting something like that in production.
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#98Earlier quoted context omitted.
Swarm works, but has poor support for volumes - which means it's tricky to run legacy applications on swarm (which eg uploads files to local disk, not s3 - or keeps state/cache on disk, not a database). Ingress is also more complicated/bespoke - the best I've found is traefik with labels for routing/config. My advice today would be to scale Docker compose vertically (eg: on a dedicated server) - then move to Kubernet…
> Swarm works, but has poor support for volumes - which means it's tricky to run legacy applications on swarm (which eg uploads files to local disk, not s3 - or keeps state/cache on disk, not a database). One way round that is to use an NFS volume. However, I've hit problems with too many client NFS connections on a docker swarm and so found it better to mount the NFS volume on each host and use a bind mount instead.
CSI support will hopefully make this easier. But: there are quite some options once you Look deeper.
Also the volume plugin spec is so simple that it is possible to maintain your own plugin (even without csi).
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#99Is 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...
yeah, I've been using this for a while now but Podman Desktop doesn't seem to care about the setting and wants to make it's own VM on my machine
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#100Why 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.
At that point you basically have a kube yaml. So might as well use that since it knows about kube things.
[deleted]