SinTan1729

For most “normal” setups, no. Networks, environment variables, volumes, permissions etc. map pretty much one-to-one.

If you’re using compose, you can even keep your setup mostly unchanged and use podman compose. Although, I would recommend learning a bit about quadlets and using them instead. There’s a tool called podlet that can help you translate your docker commands to quadlets, although it’s not complete and does miss some features. The annoying thing can be some QoL tooling that exists for docker compose that doesn’t for quadlets e.g. automatic restart for changed quadlet files. I wrote some scripts for most of these situations. I will probably release them at some point after I make sure that they don’t rely on any specific properties of my setup. But you can easily write them for yourself if you know some shell scripting.

For docker run commands, you can mostly get away with changing it to podman run.

Yes, my sister uses Gnome, and I’m basically her IT support. I just don’t see any reason for switching. It’s too limiting for me.

I also used it for a month or two on my own machine before I switched back.

I’ve been using KDE for about a decade now. It’s polished, and works well. Plus, it’s also highly customizable, so I’ve never had a reason to switch.

The question has been answered. But since you seem to be new to containers, I’ll just give you a recommendation. Just use podman. It can do pretty much everything that docker is used for, but it’s rootless by default.