yes

im not sure about ubuntu based distros. without selinux, you may not need the extra option on the volume mount.

when I moved my docker setup to a fedora coreos podman setup, the volume mounts required an additional option for a label to play nice with selinux. ‘z’ if the mount is shared between multiple containers and ‘Z’ if its just for one container.

the podman docs definitely go into more details.

ive also seen people talk on the discord about scripts that can take your yaml files and write container files to be used with podman-systemd that seemed pretty nice. i think there is also a podman-compose option out there, but I’m not super familiar with that.

i, for one, am against psychotic killers of all genders.

Aurora, its fedora kinoite (atomic w/ KDE) with some extra desktop stuff and regular flathub flatpaks.

Haha, you’re not wrong about it seeming a little extra to get installed.

I used coreos live ISO and coreos-installer with the ignition file produced from a ucore-autorebase.butane file. I lightly edited the example butane file with the ssh keys I wanted to use, password hash, and “ucore-minimal:stable-nvidia” since I’ve got an old 1060 gpu in the server for jellyfin.

proxmox is awesome, but i dont think its a right fit for what you’re looking to do. if you just want to run a few podman containers, I’d probably go with a server os that is geared towards containers.

check out fedora’s coreOS or maybe ucore from the universal blue project. it seems like they’re both good candidates for podman. i think opensuse has a similar offering in microOS.

i recently migrated containers from an older Ubuntu server running docker to a ucore server with mainly rootless podman containers. i think I prefer ucore as updates are automated, reboots are scheduled for off hours, and the podman containers are kept updated by systemd service. and cockpit comes on the os image container, so i can poke stuff on a webpage too I guess.

ah I missed that part.

why not just NFS or smb in a tailscale network?

ah you may need to make sure the pods are added to the network. i specified the network in the .pod quadlet.

im kinda digging the podman network setup as I dont have to map a bunch of port 80s to ports on the host and keep track of them. i can just tell the proxy whatever service is running on http://{container_name}:80. that is, after I found out I needed to make a new podman network because the default “podman” network doesn’t do DNS lol.

i too am on the docker to podman quadlet train! i switched from a ubuntu server running docker to a pretty stock ucore server with podman.

i put all my containers in a podman network. im using nginx proxy manager with inside ports 80, 81, and 443 mapped to 9080, 9081, and 9443 to keep the container rootless. i have the firewall configured witn port forwarding 80, 81, and 443 back to 9080, 9081, and 9443.

ucore is from the universal blue project and based on fedora’s coreos, so it comes with firewalld instead of ufw.

I like proxmox, but it kinda sounds like you’d be just fine with just docker running on opensuse or debian. Or whichever the favorite container is these days (idk why podman is so great, but I seent some posts about people that love it.)

I have tiered out my server with all my app services (jellyfin, nextcloud, etc) running in docker on a debian vm, then have lxc containers for nfs, VPN, etc. Proxmox itself handles ZFS, but I’m sure that’s bad practice and there is probably a better way - but it works for me so 🤷.

I’ve also got a opnsense vm, but not used for any “production” atm; just checking it out to see if I should switch my pfsense box over.