Live data from Hacker News

Podman v6.0.0

blog.podman.io

111–120 of 269 posts

Re: Podman v6.0.0

#111

Earlier quoted context omitted.

been using orbstack but this smol stuff is interesting is this firecracker or total rewrite

author of smol machines here, it has no relation to firecracker. It runs ontop of the libkrun vmm forked with optimizations, which is the underlying lib powering podman as well. open source, will contribute upstream when possible: https://github.com/smol-machines/libkrun

Upthread the implication seems to be that smolmachines would be in some way a replacement for orbstack to run docker containers

But it seems more like a completely different way to run isolated workloads?

Re: Podman v6.0.0

#112
post #99
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…

> the idea of dealing with systemd unit files or kublet configs, and having to created dedicated local service accounts Podman does not require systemd (thank God). I use a simple podman compose up/down in a user systemd file to automatically bring my containers up at boot, but other mechanisms are possible, like quadlets and init scripts.

Well, but that's kinda the point, isn't it? You know that other mechanisms are possible, but you opted out for a user systemd file. I know that too, and I also just use systemd for that. Because the alternative doesn't look much easier. I guess it makes sense that they try to discourage it now, because for serious deployment it isn't the best option. But when I install Podman on my laptop, I really wish the systemd configs would be added automatically without me even knowing.

I mean, really, if we keep in mind that formally these are 2 totally unrelated projects, it's hard to complain. Yes, it's almost seamless. But since when installing Podman everyone thinks roughly "I am installing a newer better Docker version", and we all already have a few dozens of custom Docker containers running, it's hard no to wish it was even more seamless and backwards-compatible. I remember the transition process wasn't nearly as smooth as I hoped, and every small glitch is kinda stressful, because you know that currently all of it "somehow works", and if something breaks you probably won't even notice right away.

Re: Podman v6.0.0

#113

Earlier quoted context omitted.

been using orbstack but this smol stuff is interesting is this firecracker or total rewrite

author of smol machines here, it has no relation to firecracker. It runs ontop of the libkrun vmm forked with optimizations, which is the underlying lib powering podman as well. open source, will contribute upstream when possible: https://github.com/smol-machines/libkrun

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

Re: Podman v6.0.0

#114
post #4

No idea why Docker is still so much more popular than Podman. Podman is obviously the better implementation. The new network stuff is a welcome improvement.

Colima just seems to be easier to work with using Docker.

Devcontainers work without having to pass special arguments and deal with inconsistent stuff once in the devcontainer itself.

K3d is easier to work with Docker.

Docker locally just makes sense.

Re: Podman v6.0.0

#115
post #4

No idea why Docker is still so much more popular than Podman. Podman is obviously the better implementation. The new network stuff is a welcome improvement.

[deleted]

Re: Podman v6.0.0

#116
post #4

No idea why Docker is still so much more popular than Podman. Podman is obviously the better implementation. The new network stuff is a welcome improvement.

I went all in on podman compose last year but went all back because off constant permission errors. I thought it was going to be better than docker because I run the containers as a user… but man the amount of time I wasted on files that either I or the container itself or some other container couldn’t read… With docker I felt that stuff just works.

And then there are the extra steps: Enable user lingering, make a systemd service that starts the compose containers (and there is nothing really “native”, it’s a script.) With Docker compose containers just restart if you say so in the file.

There are many great things about podman, will try again in a year or so perhaps?

Re: Podman v6.0.0

#117
post #4

No idea why Docker is still so much more popular than Podman. Podman is obviously the better implementation. The new network stuff is a welcome improvement.

I went all in on podman compose last year but went all back because off constant permission errors. I thought it was going to be better than docker because I run the containers as a user… but man the amount of time I wasted on files that either I or the container itself or some other container couldn’t read… With docker I felt that stuff just works. And then there are the extra steps: Enable user lingering, make a sy…

what kind of stuff is in your compose?

Re: Podman v6.0.0

#118
post #82
post #4

No idea why Docker is still so much more popular than Podman. Podman is obviously the better implementation. The new network stuff is a welcome improvement.

Isn't Docker is basically a front end to containerd, the most common k8s container runtime? One could just as well ask why use a completely separate container stack just for local development when docker shares the same business end as the prod environment.

I mean, one answer is that docker configuration on your local dev machine can go one of two ways:

1. You have to use `sudo` for every `docker ...` command; or

2. You add your user to the `docker` group and now anything that can run as your user can use docker to read or write any file on your system, making docker into the best local privilege escalation option out there.

Re: Podman v6.0.0

#119
If any Podman engineers are here: does the new /libpod/local/artifacts/add endpoint let me ingest individual layers? I have an alternative pull client that's currently a little hamstrung on Podman compared to docker+containerd, due to having to convert the entire image to tarball to ingest rather than only new layers.

Re: Podman v6.0.0

#120
post #4

No idea why Docker is still so much more popular than Podman. Podman is obviously the better implementation. The new network stuff is a welcome improvement.

Yeah, a great developer I know showed me how he could use it to get a safe dev container for Claude Code, in a way that wasn't doable with Docker.
Post reply on HN