←back to thread

1101 points codesmash | 1 comments | | HN request time: 0s | source
Show context
idoubtit ◴[] No.45137993[source]
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).

replies(2): >>45139806 #>>45143414 #
rsyring ◴[] No.45139806[source]
> 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/rootles...

replies(1): >>45139917 #
codedokode ◴[] No.45139917[source]
The slow speed is for using slirp4netns, not containers in general.
replies(1): >>45146160 #
1. gm678 ◴[] No.45146160{3}[source]
(and to be clear, podman 5.0 changed the default from slirp4netns to passt/pasta in 5.0)