Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Podman v6.0.0

blog.podman.io

Post reply on HN
Print view View original

151–160 of 269 posts

Re: Podman v6.0.0

#151

Post by thewisenerd »

podman's been great for me on macOS for testing stuff quick; which earlier used to need a whole limactl[3]/virt thing.

you can set it up with qemu-user-static for --platform linux/amd64; i don't remember which i exactly used, or if official docs have been updated for it but looked something like [1]

there is one sneaky bug in qemu that breaks uv [2] for cross-platform targets so i keep having to fall back to lima for that, but great otherwise.

[1]: https://www.itix.fr/blog/qemu-user-static-with-podman/ [2]: https://github.com/astral-sh/uv/issues/16024 , https://gitlab.com/qemu-project/qemu/-/work_items/3130 [3]: https://lima-vm.io/

Re: Podman v6.0.0

#152

Post by rsyring »

stryan wrote: post #150
rsyring wrote: post #149

As long as they refuse to support installing on Ubuntu (and other popular distros), without relying on the distro repos which are always out of date, they will continue to lose to Docker. Any serious project in this space supports as many distros as possible. It's OSS, so I'm not complaining per se, I have no right to. They owe me nothing. But this one issue has kept me from seriously considering Podman for years. Th…

To be clear, it doesn't explicitly not support Ubuntu or anything, it just doesn't privilege it. Podman doesn't produce packages for any distros.

Agreed. But, IMO, it looks like amateur hour when you compare their stance to the distro support Docker provides.

Re: Podman v6.0.0

#153

Post by idoubtit »

LinXitoW wrote: post #129
asa977 wrote: post #57

Earlier quoted context omitted.

We moved from docker to podman about 15 months ago, and I'm never going back. I (personally) love the quadlet (read: systemd) integration, that makes it so much easier to monitor a set of running services, be they regular systemd services or containers. Running rootless is as straightforward as it gets and on top of it, podman is blazingly fast. I, personally, don't miss docker compose all that much, but I understand…

The one big reason I dread giving up compose files is that they're a great way to have system agnostic documentation on how to setup a new stack. That means every developer can just start the thing locally, and it's pretty much the same as on the server (and everyone elses laptop). Podman doesn't officially support any thing platform agnostic. How do you (or anyone) deal with this for a project in active development?

podman can work with kube files, which is the YAML format from Kubernetes. That's more "platform agnostic" than docker-compose. And it can be read as a documentation in the same way.

Re: Podman v6.0.0

#154

Post by hiciu »

LinXitoW wrote: post #128
sudonem wrote: post #73

Earlier quoted context omitted.

I’d wager it’s mainly just that deployment is mildly more annoying and requires more disparate steps. Especially if you want to go rootless (and you should). For someone that isn’t “Linux first” (like a baby developer learning to containerize their apps), the idea of dealing with systemd unit files or kublet configs, and having to created dedicated local service accounts (and remembering to enable linger) is somewhat…

It's not just mildly annoying, it completely ruins a great thing. Docker Compose is to stacks what Dockerfiles are to a single application. Podmans solution is to not commit to compose, but instead to create a bespoke mechanism involving a bunch of tiny files, all of which is insanely system (linux) specific, and therefore completely non-portable. I genuinely don't understand how someone can see the value of Docker,…

FWIW, for me docker compose works just fine with podman. I am not sure what kind of additional configuration is needed these days, make sure you are running podman with the socket thing and perhaps set DOCKER_HOST. It's just a client / frontend to an API that podman provides.

Re: Podman v6.0.0

#155

Post by jrmg »

sudonem wrote: post #96
tormeh wrote: post #92

Earlier quoted context omitted.

Are we talking windows here? On Linux and Mac I believe you can install Podman via a package manager like anything else.

Linux. It’s not the installation of podman that can be fiddly. It’s the setting up systemd unit files and local user accounts for rootless / daemonless deployment of containerized apps that can be a headache. It’s not hard. It’s just fiddly.

You can just run podman containers as root if you don’t want the fiddllyness of user accounts - it’s no less secure than rootful Docker.

Re: Podman v6.0.0

#156

Post by drnick1 »

sudonem wrote: post #142
drnick1 wrote: post #100

Earlier quoted context omitted.

> It’s just fiddly. You could quite simply have a systemd file that calls podman compose up when the service starts and podman compose down when it stops. Basically the same systemd file for every container stack defined in a single compose.yml. It's extremely easy, and does not do stuff behind your back like Docker (such as silently altering iptables rules).

Sure. But that wasn’t OP’s question. The question was why Podman doesn’t have the adoption levels that Docker does, and my supposition was that (for those that don’t have much Linux administration experience) added steps like systems configs, or quadlets etc are just another barrier to entry that you don’t have with Docker. I’m not arguing that Docker is better (I think Podman wins in a lot of ways actually) just tha…

I think it's just because Docker came before. Podman is more secure and architecturally cleaner, but not touching something that works is an equally good reason not to migrate.

Re: Podman v6.0.0

#157

Post by davkan »

hoppp wrote: post #68
theK wrote: post #56

Earlier quoted context omitted.

Last time I checked podman compose was only a superficial docker compose equivalent. Also stuff like inotify seems to randomly break a lot on the podman side. I'd love to be able to recommend people use podman but not having a good docker compose compatibility and missing inotify on volumes makes the DX just too problematic.

Check again? I don't have any issues like this and use podman compose in prod.

It was a pain when i tried it like 5 years ago for what it’s worth.

Re: Podman v6.0.0

#158

Post by zuzululu »

binsquare wrote: post #134
zuzululu wrote: post #113

Earlier quoted context omitted.

good stuff man i just installed it and its super fast im just not sure is this really secure to run untrusted code i can't find any white papers

the underlying vmm is libkrun: https://github.com/libkrun/libkrun is battle tested and used for podman. It provides kernel isolation for running untrusted code which is a security boundary that traditional containers can't guarantee. I'm engaged with a third party security penetration company for their review, and will be happy to share it publicly when it is available.

thank you. definitely enjoying smol. this is a very nice alternative to docker, orbstack even firecracker

Re: Podman v6.0.0

#159

Post by dockerimage »

ffsm8 wrote: post #28
q8zd3 wrote: post #7

Earlier quoted context omitted.

it has a stronger brand, probably because it was created first. I still hear the term "docker container" (sometimes).

> sometimes I've never interacted with anyone that knew them by another name. It's always (docker) container, where they may leave out the docker term, but if questioed what kind of container they mean theyll say it. And the times I've called them OCI container (or image when talking about those) nobody knew what I meant until I clarified to docker

I hear occasionally Image Container, but even that is fundamentally docker flavored because when disambiguating for the term "image".

This comes up because we use both the Image and Package registries on Gitlab, so we sometimes have to absolutely specify, and the conversation lends to "The Docker Image one".

Re: Podman v6.0.0

#160

Post by kccqzy »

roger_ wrote: post #6

Anyone have experience switching from Docker to Podman? I have a lot of compose files in my homelab/automation setup and those are what I’m most concerned about.

I moved in 2021.

Others have pointed out that you can use podman-compose or docker-compose pointed at podman. I did something different: I switched to using systemd to manage all my containers. It was worthwhile as I can just use my usual systemctl and journalctl utilities for both containerized and non-containerized services rather than having to remember two sets of commands.

I only experienced one minor issue with pasta (used by podman) with networking, but by then I had fully committed to podman so I did not even try to see whether I would have had this same issue if I were using docker.

Post reply on HN