EDIT: For some context, I recently gave podman another go. I have a few services on my homelab server set up in docker containers, so I tried migrating to podman.

After the second major bug (open issue on github) I encountered looked like it would require completely dropping using compose files to work around, I gave up and went back to docker.

I like the idea of podman, but it’s just not stable. I’ll try again in a year or so.

As a bonus, docker’s CLI is significantly nicer.

  • esc@piefed.social
    link
    fedilink
    English
    arrow-up
    55
    arrow-down
    1
    ·
    3 days ago

    Rootless, better integrated with system, a bit faster and lighter on resources. Also it supports k8s style yaml configuration both ways and a lot of people are more familiar with them and they also provide some (minimal) interoperability.

    • katze@lemmy.4d2.org
      link
      fedilink
      arrow-up
      9
      arrow-down
      8
      ·
      3 days ago

      a bit faster and lighter on resources.

      Can’t confirm. I have two VMs with an identical image (about 200 MB).

      Docker: Pulling the image takes about 10 seconds and needs about 200 MB diskspace.

      Podman: Pulling the image takes about 15 minutes and needs about 110 GB diskspace.

      Docker: Commands like “docker ps”, “docker stop” etc. run in a few seconds.

      Podman: Commands like “podman ps”, “podman stop” etc. take at least one minute.

      • esc@piefed.social
        link
        fedilink
        English
        arrow-up
        27
        arrow-down
        4
        ·
        3 days ago

        Company confirmed that it is lighter and faster with multiple benchmark at the time of migration. Your case sounds like extreme misconfiguration.

        • katze@lemmy.4d2.org
          link
          fedilink
          arrow-up
          3
          ·
          3 days ago

          extreme misconfiguration

          I did not configure anything, I just installed it from the debian repository.

          • Klara@lemmy.blahaj.zone
            link
            fedilink
            arrow-up
            10
            ·
            edit-2
            3 days ago

            If this is on Debian 12 I think the issue is that the default storage backend is VFS rather than Overlay, which burnt me as well as it is REALLY inefficient. Look up how to find out what you’re using and change it if that’s it. After doing that it’s been really good for me :)

      • Allero@lemmy.today
        link
        fedilink
        arrow-up
        19
        arrow-down
        2
        ·
        3 days ago

        Something is super wrong in your setup or some weird Podman bug on your side. Works flawlessly and quickly on my machine, no such issues.