I am already fairly comfortable using docker and its tool set. Is the tide shifting towards Podman? Should I start learning how to use Podman? Thanks in advance.
I am already fairly comfortable using docker and its tool set. Is the tide shifting towards Podman? Should I start learning how to use Podman? Thanks in advance.
I can’t help but laugh at this.
“learn how to use podman” from someone who already knows docker is their happy path.
https://docs.podman.io/en/latest/index.html#what-is-podman
Seriously, the only two problems i’ve had are:
I would consider myself a very beginning docker user so I’ve a long way to go but I can see, given that I am a beginner, it might make sense to pivot now to Podman.
It might be easier to learn some docker first. That’s what all the documentation is written for and I’ve found the “alias docker to podman and call it a day” approach to be overly optimistic.
conversely, switching now means he’ll be learning domain specific knowledge for podman, the thing he wants to work in, and not building it in docker, the thing he’s trying to move away from
I did need to install some additional stuff to get docker-compose working with podman, and I needed to make sure I ran those things as a user instead of as root to make sure that the containers created by docker-compose were running rootless. But I do have my Lemmy instance running with rootless containers using podman.
My next step is to convert it to a systemd service, but I just haven’t got there yet.
But is it really a drop-in replacement for docker? Networking seems fundamentally different.
I tried to use a docker compose file for Wordpress as an example, with nginx-proxy-manager in another compose file. They’re linked together through an external network.
Podman works differently. You’re expected to create ‘pods’. I’m not super clear on this (just dipping my toes) but podman seems to be an alternative to k8s, not docker.
That’s the claim but buildx is extremely limited on podman.