4 ms·
I also ditched docker when I could. In my experience... Podman with pods is a better experience than docker-compose. It's easy to interactively create a pod an
by idoubtit 1y ago
I also ditched docker when I could. In my experience...
Podman with pods is a better experience than docker-compose. It's easy to interactively create a pod and add containers to it. The containers ports will behave as if they were on the same machine. Then `podman generate kube` and you have a yaml file that you can run with `podman kube play`.
Rootless networking is very slow unless you install `passt`. With Debian, you probably should install every optional package that podman recommends.
The documentation is lacking. Officially, it's mostly man pages, with a few blog posts announcing features, though the posts are often out of date.
Podman with its docker socket is often compatible with Docker. Even docker-compose can (usually) work with podman. I've had a few failures, though.
Gitlab-runner can use podman instead of docker, but in this case the is no network aliases. So it's useless if the runner needs to orchestrate several images (e.g. code and db).
- rsyring 1y ago> Rootless networking is very slow I came across just how slow recently: - Container -> host: 0.398 Gbps vs. 42.2 Gbps - host -> container: 20.6 Gbps vs 47.4 Gbps Source: https://github.com/containerd/nerdctl/blob/main/docs/rootless.md#bypass4netns https://github.com/containerd/nerdctl/blob/main/docs/rootles...
- codedokode 1y agoThe slow speed is for using slirp4netns, not containers in general.
- gm678 1y ago(and to be clear, podman 5.0 changed the default from slirp4netns to passt/pasta in 5.0)
- gucci-on-fleek 1y ago> Rootless networking is very slow unless you install `passt`. If the software that you're running inside the container supports it, you can use socket activation [0] to get native performance. [0]: https://github.com/containers/podman/blob/main/docs/tutorials/socket_activation.md https://github.com/containers/podman/blob/main/docs/tutorial...