Earlier quoted context omitted.
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.
thanks, and my bad for not reading carefully
Podman Desktop 1.2 Released: Compose and Kubernetes Support
111–120 of 132 posts
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#112Earlier quoted context omitted.
> 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.
What are some of the most common use cases you can think of, like the most popular ones? I'm drawing a blank on how I'd use this.
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#113Earlier quoted context omitted.
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.
Yeah, so it's Virtual Box using your resources, not Vagrant or Docker. You might want to read up a bit on how containers work -- on a unix system, assuming same cpu architechture (so you don't need a VM) and filesystem that supports overlays, containers have barely any overhead in terms of system resources. You could have a thousand containers running on your machine and be fine. VMs, on the other hand, have pretty serious overhead.
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#114Earlier quoted context omitted.
Surprised to hear you think debugging in kubernetes is maddening. It’s absolutely very different , but if I had to debug a system I knew nothing about, I’d rather debug a kubernetes based system rather than any other. Standards and all that. Anyways - for a single container or two obviously you’re right - I’m just not sure that’s so common outside of a side project anymore.
Especially because "production" implies an ingress controller, monitoring, etc. Does a Docker Compose-based production setup contain run its own Nginx with its own manually-wired rules? Its own Prometheus?
I'd wager most production systems don't have those.
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#115Earlier quoted context omitted.
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.
What are some of the most common use cases you can think of, like the most popular ones? I'm drawing a blank on how I'd use this.
We use a few operators currently.
- Prometheus operator
Lets us spin up a prometheus monitoring stack on our kubernetes cluster for monitoring metrics and scraping metrics from our services pretty much automatically.
- Thanos Operator
Spins up prometheus monitoring aggregations across multiple clusters with object storage backends, basically you can store metrics for years and query them with grafana.
- Strimzi Operator (Kafka)
Orchestrates a kafka cluster for kafka connect or even full blown kafka brokers with zookeeper.
- Istio Operator
Builds a service mesh on the cluster, offering MTLS and an envoy load balancer with some incredible flexibility
- Cert-manager operator
Lets us auto-generate certificates for resources via letsencrypt. This one is so nice for internal services and keeps certs valid without any hand holding
- Argo CD operator
We use this operator to deploy argocd pipelines and ship new services and updates via github actions in a very standardized way, and gives our users a UI to see what's going on.
- Actions runner controller
Using this actions runner controller we can offload github actions runners to self-hosted runners that automatically scale for pipeline workloads. Another set up and forget system and saves us from buying more github actions minutes.
Ultimately we use a ton of operators because it gives us an out of the box framework for tooling we need to deploy without reinventing the wheel. Of course some operators aren't worth using and it's definitely worth checking them out to see if they worth your time. A lot of them are really open to updates and changes also so you can help evolve them as you grow into other cases.
I will say, it's very important to understand what you are abstracting with these, you can absolutely blindly deploy services with operators and have it blow up in your face if you aren't sure what's going on behind the scenes or lack distributed service knowledge in production.
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#116I 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…
Do you run with Docker daemon running in rootless mode? Does rancher default to rootless mode? I hear Docker can run in rootless mode but does anyone really run it that way. If I want to start a single container in my homedir, I need to start up multiple docker daemons (dockerd, containerd) to run and then they run forever even if I run in daemon mode. Or I can shut them down until I need to interact with the container again.
Have you tried running with Pods? Have you tried Quadlet? Have you tried to generate kube yaml from running pods and containers on your system? Have you used podman to generate pods and containers from existing kubernetes yaml files? Have you launched containers each in their own User Namespace with --userns=auto?
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#117Earlier quoted context omitted.
All of that can be accomplished by being compatible with the broader OCI ecosystem. But Red Hat explicitly tries to be a Docker replacement (they suggest `alias docker=podman`, which actually breaks in many ways), to the point where I'm not sure why I should bother using a product that will always play catch-up to the real thing. This Desktop and Compose announcement is part of that roadmap, and I'm just wondering wh…
I find the Pod and Deployment support in Podman to be a killer feature personally. I've also gotten small apps running manually in podman, and once the config is working, podman can emit k8s compatible yaml that can be re-applied to a different podman or applied to a k8s cluster. Pretty sweet IMHO.
That's a good point, thanks. I haven't yet experimented with that.
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#118Earlier quoted context omitted.
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.
Statements like these offer zero value, maybe you could qualify it with some reasoning?
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#119I'm not happy with Podman Desktop's Svelte GUI.
Antd or MUI (React) feel much more mature.
But they are working on it.
Re: Podman Desktop 1.2 Released: Compose and Kubernetes Support
#120Earlier 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
Dev here — there's a lot more special sauce than that! https://docs.orbstack.dev/architecture