>>108788185
Docker because by the time I first tried podman I had already been using docker for two years, and figured out workarounds for everything that bothers me about it. Have no compelling reason to switch.

If you are just starting with containers there's no reason not to go rootless podman, even better with quadlets if you use systemd (I dont ofc, i use the oci guix service)

File: file.png (331 KB, 1040x706)

331 KB PNG

I just use GNU Guix and call it a day.

I use podman/toolbox on Fedora Silverblue because that's the recommended solution.

>>108788185
podman because i run fedora but i rarely use it
ive recently tried docker swarm a bit and took a dive into k3s now i have a cluster of SBCs (radxa,raspberry,orangepi) and im running shit on them

>>108788185
Podman is globohomo trash that depends on systemd.

Docker is marginally better.

>>108788185
i started with podman and i would feel dirty using docker now
yes im unemployed
also why the fuck does aardvark-dns keep my systemd socket ports i open and fork to the container hostage when the container has two networks - one internal and one external, with one of those having the dns-enabled option set as true. restarting the container fails with ports already in use
also, how the fuck do i allow these forked sockets to work with selinux? audit2allow screams some obscenities at me and leaves me with no module at all... i've been running permissive ever since i moved

>>108788185
binaries and daemons

>>108788185
Both sucks.

>>108788185
apptainer or singularity

I use Docker Compose for both local dev and production (we don't need high availability). I can declare a whole stack in one file, or I can split it into a few files and reuse parts between dev/prod configs. Everything gets brought up or down with one command. As long as containers have restart=unless-stopped, everything comes back up on reboot with no need to write any separate systemd stuff.

The last time I checked, podman doesn't have anything comparable to this except some buggy half-hearted attempts at a "podman-compose" wrapper script. Quadlet files are basically mini-systemd configs, much more tedious to write than docker-compose and not really intended for development. And I don't think you can bring everything up/down with one command unless you do some hairy dependency stuff.

Anything I'm missing? docker-compose works so well that I tend to just assume everyone uses it, and so the lack of it in the podman ecosystem feels like a huge unacceptable gap to me. Obviously other people must be using containers differently because I don't hear this talked about much when people discuss docker vs podman.

Quadlets seemed cool until I actually used them and then I remembered that systemd sucks. I do use systemd but I just don't want to have to write a systemd config for every container I use. Especially when they get more complicated and depend on other containers.

Docker compose works great and is much easier. Plus everyone has example compose files for their containers to get you started.

Podman because of the integration with systemd.
systemd is probably the best thing that ever happened to linux servers

what do you guys do with these?

>>108789351
Other people have infrastructure deployed on baremetal or with other constraints and can't just cram it all into one definition file. Hopefully you at least don't put your fucking database passwords in there in plain text.

More than once I've had to unpack some garbage app that only shipped with a docker-compose file in order to deploy it in the existing environment.

>>108788185
Correction OP
>PodWoman

>>108788185
Docker for dev
Podman for production

>>108789542
I run my whole media acquisition+streaming stack in docker. search+discovery, automatic torrent grabbing, automatic search, automatic rename and taging, picked up by jellyfin.

>>108788185
Portainer

>>108788185
containers?

>>108788889
>Podman is globohomo trash that depends on systemd.
it doesnt docker

>>108789861
what images do you use

>>108788185
for macOS the answer is orbstack, which fixes all the shit parts of Docker Desktop while retaining full API compatibility