Docker or podman?

⁨57⁩ ⁨likes⁩

Submitted ⁨⁨1⁩ ⁨month⁩ ago⁩ by ⁨noodles@lemmy.world⁩ to ⁨selfhosted@lemmy.world⁩

I would love to hear everyone’s opinion.

source

Comments

Sort:hotnew top

Ledivin@lemmy.world ⁨1⁩ ⁨month⁩ ago
If you don’t have strong opinions one way or the other, then docker is the easy answer. Way, way more widespread, which generally tends to mean better docs, more guides and examples, more tooling and open-source support…

source
Molecular0079@lemmy.world ⁨1⁩ ⁨month⁩ ago
I use podman with the podman-docker compatibility layer and native docker-compose. Podman + podman-docker is a drop-in replacement for actual docker. You can run all the regular docker commands and it will work. If you run it as rootful, it behaves in exactly the same way. Docker-compose will work right on top of it.

I prefer this over native Docker because I get the best of both worlds. All the tutorials and guides for Docker work just fine, but at the same time I can explore Podman’s rootless containers. Plus I enjoy it’s integration with Cockpit.

source
sudneo@lemmy.world ⁨1⁩ ⁨month⁩ ago
I would say Docker. There is no substantial benefit in running podman, while docker is a widely adopted tool (which means more tooling in the ecosystem, easier to find answers to questions etc.). The difference is not huge tbh, and some time ago the biggest advantage for podman was being able to run rootless, while docker was stuck with a root daemon. This is not the case anymore (docker can run rootless), so I would say unless you have some specific argument to use podman, stick with docker.

source
rentar42@kbin.social ⁨1⁩ ⁨month⁩ ago
I personally prefer podman, due to its rootless mode being "more default" than in docker (rootless docker works, but it's basically an afterthought).

That being said: there's just so many tutorials, tools and other resources that assume docker by default that starting with docker is definitely the less cumbersome approach. It's not that podman is signficantly harder or has many big differences, but all the tutorials are basically written with docker as the first target in mind.

In my homelab the progression was docker -> rootless docker -> podman and the last step isn't fully done yet, so I'm currently running a mix of rootless docker and podman.

source
matcha_addict@lemy.lol ⁨1⁩ ⁨month⁩ ago
Podman is slightly better, but most tutorials are for docker.

So, podman if you’re comfortable looking through docs, man-pages, scarce Internet resources, and trial and error for finding things out. Especially if you care about having better security with rootless mode.

Podman also has a different way for managing many containers at once, and the interaction between them.

source
Static_Rocket@lemmy.world ⁨1⁩ ⁨month⁩ ago
It depends on what you want. Do you want containers that don’t blow away your firewall? Podman is nice, but docker can be configured a little to avoid this. Want things that autostart and don’t have issues with entry points that attempt to play with permissions/users? Docker or podman as root is necessary. Want reasonable compose support? Podman now needs a daemon/socket. Want to make build containers and not deal with permission/user remapping at all? Podman is really nice.

Do not attempt to use podman-compose. That app is dead.

source
dandroid@sh.itjust.works ⁨1⁩ ⁨month⁩ ago
I like podman because rootless and daemonless are built-in and default. Yes, it can be done on docker, but you have to do a bunch of shit to get it set up.

You could create the alias alias docker=“podman” and 99% of the time, you won’t even be able to tell the difference since podman is a docker drop in replacement. All the docker documentation applies to podman as well. But since docker runs as root by default, some edge cases might not work out of the box (like binding to a port on the host less than 1000).

Podman comes with some neat tools like being able to create systemd service files to start and stop containers as services.

To use docker-compose, you’ll need some additional packages. That’s probably the biggest drawback to podman imo. Podman wants to use pods instead of docker-compose, but I think they gotta take their heads out of their asses and just support the more popular format on that one. Not to mention docker-compose is just plain better imo. Easier to define, easier to understand, easier to modify. The list goes on and on.

source
- vegetaaaaaaa@lemmy.world ⁨1⁩ ⁨month⁩ ago
  
  You could create the alias alias docker=“podman”
  
  There’s even an official Debian package that takes care of this for you: packages.debian.org/bookworm/podman-docker
  
  source
  - dandroid@sh.itjust.works ⁨1⁩ ⁨month⁩ ago
    That package actually does a bit more than that! If you don’t need all the extras, then I say just add the alias and be done with it.
    
    source
chiisana@lemmy.chiisana.net ⁨1⁩ ⁨month⁩ ago
If docker works for you, then don’t change what’s not broken. If there are things you don’t like about docker (root access etc for example) then venture out and try others. At the end of the day, they’re just tools to get to the more interesting stuff — actually running applications and playing with them.

source
- fmstrat@lemmy.nowsci.com ⁨1⁩ ⁨month⁩ ago
  Just pointing out your response may be dated. Docker can run rootless: docs.docker.com/engine/security/rootless/
  
  source
kevincox@lemmy.ml ⁨1⁩ ⁨month⁩ ago
I would say podman by default. It has a better security architecture as it can run rootless.

However there are small differences from Docker so you may need use Docker if you are trying to run third-party services that rely on these differences.

source
MangoPenguin@lemmy.blahaj.zone ⁨1⁩ ⁨month⁩ ago
I like the idea behind Podman, but it’s not a suitable drop in replacement for Docker yet. Especially since it requires manual setup to auto-start stacks at boot, and can’t import docker compose files easily.

source
- dragnucs@lemmy.ml ⁨1⁩ ⁨month⁩ ago
  There is now podman compose that can read and use docker-compose files. As for importing, I cannot tell.
  
  source
falcon15500@lemmy.nine-hells.net ⁨1⁩ ⁨month⁩ ago
Podman rootless, using quadlets for systemd services. :D

source
CriticalMiss@lemmy.world ⁨1⁩ ⁨month⁩ ago
I use Docker exclusively. Podman is the NIH syndrome response to an industry standard. It has its benefits but Docker just works.

source
- FooBarrington@lemmy.world ⁨1⁩ ⁨month⁩ ago
  Podman wasn’t built due to NIH. Docker has real problems (though many have been fixed), and Podman was built to fix those.
  
  source
  - CriticalMiss@lemmy.world ⁨1⁩ ⁨month⁩ ago
    Docker Engine is open source. They could’ve easily contributed patches to it which just further proves that it is a NIH syndrome response.
    
    source
    -> View More Comments
titey@jlai.lu ⁨1⁩ ⁨month⁩ ago
Podman. This is the way.

source
lemmyvore@feddit.nl ⁨1⁩ ⁨month⁩ ago
If you’re just starting out and have never used containers before start with regular (rootful) docker. It’s a much simpler mechanism to understand for a beginner and has more widespread support and documentation.

Once you understand containers and have used them for a few months you can start going down the rabbit hole, there’s no shortage of technologies to explore.

Or, if you’re only interested in self-hosting as a hobby and docker does what you need, you can also stop there. Not everybody needs a deep dive into technology.

source
Shimitar@feddit.it ⁨1⁩ ⁨month⁩ ago
Definitely podman + podman compose.

Its fully open source (docker isn’t) and its secure by design (security has been added to docker as an after fought).

Also podman is rootless by design, docker takes a bit of effort to run root less.

source
WeLoveCastingSpellz@lemmy.dbzer0.com ⁨1⁩ ⁨month⁩ ago
I like podman more because people told me it was better and it just worked for me :P

source
BentiGorlich@gehirneimer.de ⁨1⁩ ⁨month⁩ ago
Honestly I use docker because by now I know docker and basically everything has support for it...

source
atzanteol@sh.itjust.works ⁨1⁩ ⁨month⁩ ago
Whichever one you want.

source
PoliticallyIncorrect@lemmy.world ⁨1⁩ ⁨month⁩ ago
I use Docker and it works for what I use it so I have no need to change it, maybe if in the future I have the need to use rodman I would consider to change. But right now I’m not interested.

source
genie@lemmy.world ⁨1⁩ ⁨month⁩ ago
What no love for Incus round these parts?

source
- sudneo@lemmy.world ⁨1⁩ ⁨month⁩ ago
  Because the lxc way is inherently different from the docker/podman way. It’s aimed at running full systems, rather than mono process containers. It has it’s use cases, but they are not as common IMHO.
  
  source
  - genie@lemmy.world ⁨1⁩ ⁨month⁩ ago
    Real men use Incus NixOS containers for reproducible builds instead of wimpy dockerfiles 😤😤
    
    /s – for real though, I hope someday you finally remove the stick from where the sun doesn’t shine ;)
    
    source
    -> View More Comments
Hawk@lemmynsfw.com ⁨1⁩ ⁨month⁩ ago
They both kind of suck in their own way.

If you want to things to run at startup and you’re not on systemd, rootless docker is probably easier.

Otherwise podman is mostly fine but be careful of native overlay if you’re not on BTRFS, this causes some pretty long build times.

source
- Shimitar@feddit.it ⁨1⁩ ⁨month⁩ ago
  Takes 1 minute to write a non systemd startup script, come on.
  
  I understand systemd “spoiled” people, but not having a potentially insecure always running daemon for no purpose at all (docker) beat the alternative for me.
  
  source
rizoid@lemmy.dbzer0.com ⁨1⁩ ⁨month⁩ ago
Docker is a great choice with lots of good tutorials. I personally use podman since all my servers are now running Fedora server and podman is installed by default.

source
AustralianSimon@lemmy.world ⁨1⁩ ⁨month⁩ ago
No love for kubernetes?

source
- sudneo@lemmy.world ⁨1⁩ ⁨month⁩ ago
  I think k8s is a different beast, that requires way more domain specific knowledge besides server/Linux basic administration. I do run it, but it’s an evolution of a need, specifically when you want to manage a fleet of machines running containers.
  
  source
  - AustralianSimon@lemmy.world ⁨1⁩ ⁨month⁩ ago
    Can be ott yeah. I set mine up to understand how it all works and just kept things going.
    
    source
  - anzo@programming.dev ⁨1⁩ ⁨month⁩ ago
    Even then, there’s dockerswarm.rocks (linking directly to tutorial to show how easy it is!)
    
    source
    -> View More Comments
- 69420@lemmy.world ⁨1⁩ ⁨month⁩ ago
  Kubernetes? I’ve never even seen her netes.
  
  source
tagginator@utter.online [bot] ⁨1⁩ ⁨month⁩ ago
New Lemmy Post: Docker or podman? (https://lemmy.world/post/13073444)
Tagging: #SelfHosted
(Replying in the OP of this thread (NOT THIS BOT!) will appear as a comment in the lemmy discussion.)
I am a FOSS bot. Check my README: https://github.com/db0/lemmy-tagginator/blob/main/README.md
source