4 ms·

Its not as easy nor as simple as docker + docker compose.

ilovecaching 4y ago
It’s literally OCI compatible, integrates with systemd and LSM, and runs rootless by default. Podman is 100000% better designed on the inside with the same interface on the outside.
- dontlaugh 4y ago
  It’s the lack of fully compatible compose that matters most.
  - jacooper 4y ago
    Podman appears to support the compose v2 spec, and the socket API, but still not fully supporting buildkit. https://www.redhat.com/sysadmin/podman-compose-docker-compose https://www.redhat.com/sysadmin/podman-compose-docker-compos...
- jacooper 4y ago
  Rootless networking is still a mess with no IP source propagation and much slower performance. So for most users docker with userNS-remapping is actually a better choice. Also systemd integration isn't a plus for me, I don't want to deal with SystemD just to have a container start on startup.
  - yrro 4y ago
    I think --network=pasta: helps with source IP preservation. Regardless that has never bothered me since I'm only using podman or docker for local development...
    - jacooper 4y ago
      Hmmm, pasta seems to solve all rootless networking issues... https://github.com/containers/podman/pull/16141 https://github.com/containers/podman/pull/16141
5e92cb50239222b 4y ago
You're right, it's both easier and simpler since no daemons are involved. podman-compose has the same command-line interface and has worked ok for me so far (maybe 3 or 4 years at this point).
- jacooper 4y ago
  Podman-compose isn't fully compatible with the new compose spec. Also I really don't care if docker has a daemon or not, for me it offers feature like auto starting containers without bothering with SystemD, and auto updates using watchtower and the docker socket. And since podman doesn't have an official distro package repo like docker, you are stuck use whatever old version shipped in your distro without recent improvements, which is important for a very active development project.
  - yamtaddle 4y ago
    > Also I really don't care if docker has a daemon or not, for me it offers feature like auto starting containers without bothering with SystemD Bingo, the "pain" of the daemon (it's never cause a single problem for me? Especially on Linux, on macOS I've occasionally had to go start it because it wasn't running, but BFD) saves me from having to touch systemd. Or, indeed, from caring WTF distro I'm running and which init system it uses at all.
    - jacooper 4y ago
      To be fair, every mainstream distro now uses Systemd
  - indymike 4y ago
    > And since podman doesn't have an official repo like docker, Hmm... https://github.com/containers/podman https://github.com/containers/podman I found that on: https://podman.io/ https://podman.io/ so, I'm pretty sure it's official.
    - jacooper 4y ago
Anarch157a 4y ago
podman + podman-compose is as easy.
- jacooper 4y ago
  Not comparable to the full compose spec.

It’s literally OCI compatible, integrates with systemd and LSM, and runs rootless by default. Podman is 100000% better designed on the inside with the same interface on the outside.

dontlaugh 4y ago
It’s the lack of fully compatible compose that matters most.
- jacooper 4y ago
  Podman appears to support the compose v2 spec, and the socket API, but still not fully supporting buildkit. https://www.redhat.com/sysadmin/podman-compose-docker-compose https://www.redhat.com/sysadmin/podman-compose-docker-compos...
jacooper 4y ago
Rootless networking is still a mess with no IP source propagation and much slower performance. So for most users docker with userNS-remapping is actually a better choice. Also systemd integration isn't a plus for me, I don't want to deal with SystemD just to have a container start on startup.
- yrro 4y ago
  I think --network=pasta: helps with source IP preservation. Regardless that has never bothered me since I'm only using podman or docker for local development...
  - jacooper 4y ago
    Hmmm, pasta seems to solve all rootless networking issues... https://github.com/containers/podman/pull/16141 https://github.com/containers/podman/pull/16141

5e92cb50239222b 4y ago

You're right, it's both easier and simpler since no daemons are involved. podman-compose has the same command-line interface and has worked ok for me so far (maybe 3 or 4 years at this point).

jacooper 4y ago
Podman-compose isn't fully compatible with the new compose spec. Also I really don't care if docker has a daemon or not, for me it offers feature like auto starting containers without bothering with SystemD, and auto updates using watchtower and the docker socket. And since podman doesn't have an official distro package repo like docker, you are stuck use whatever old version shipped in your distro without recent improvements, which is important for a very active development project.
- yamtaddle 4y ago
  > Also I really don't care if docker has a daemon or not, for me it offers feature like auto starting containers without bothering with SystemD Bingo, the "pain" of the daemon (it's never cause a single problem for me? Especially on Linux, on macOS I've occasionally had to go start it because it wasn't running, but BFD) saves me from having to touch systemd. Or, indeed, from caring WTF distro I'm running and which init system it uses at all.
  - jacooper 4y ago
    To be fair, every mainstream distro now uses Systemd
- indymike 4y ago
  > And since podman doesn't have an official repo like docker, Hmm... https://github.com/containers/podman https://github.com/containers/podman I found that on: https://podman.io/ https://podman.io/ so, I'm pretty sure it's official.
  - jacooper 4y ago

Anarch157a 4y ago

podman + podman-compose is as easy.

jacooper 4y ago
Not comparable to the full compose spec.