Running Podman in production for years now, and I don't miss the Docker daemon one bit.
-
Running Podman
in production for years now, and I don't miss the Docker daemon one bit.I just published a deep dive on managing OCI containers the Unix way: daemonless, rootless, and natively integrated with systemd via Quadlets.
I cover:
- Real secrets management
- Auto-updates via systemd timers
- The Docker compatibility layerThis is the guide I wish I had when making the switch.
Read it here: https://blog.hofstede.it/podman-in-production-quadlets-secrets-auto-updates-and-docker-compatibility/
#Podman #Linux #DevOps #Systemd #Homelab #Sysadmin #Containers
-
Running Podman
in production for years now, and I don't miss the Docker daemon one bit.I just published a deep dive on managing OCI containers the Unix way: daemonless, rootless, and natively integrated with systemd via Quadlets.
I cover:
- Real secrets management
- Auto-updates via systemd timers
- The Docker compatibility layerThis is the guide I wish I had when making the switch.
Read it here: https://blog.hofstede.it/podman-in-production-quadlets-secrets-auto-updates-and-docker-compatibility/
#Podman #Linux #DevOps #Systemd #Homelab #Sysadmin #Containers
-
@Larvitz been wondering about switching to either podman or libvirt for the plain LXC things I have on a server, because some other admins are not used to it and want GUI tools, but I suppose that means migrating… ?
@mmu_man For GUIs, there's Podman Desktop (https://podman-desktop.io) and also the web-based Cockpit Client for Podman (https://github.com/cockpit-project/cockpit-podman)
-
@mmu_man For GUIs, there's Podman Desktop (https://podman-desktop.io) and also the web-based Cockpit Client for Podman (https://github.com/cockpit-project/cockpit-podman)
-
@Larvitz yeah but it won't keep containers as is I guess, so I won't be able to keep using lxc commands directly…
-
Running Podman
in production for years now, and I don't miss the Docker daemon one bit.I just published a deep dive on managing OCI containers the Unix way: daemonless, rootless, and natively integrated with systemd via Quadlets.
I cover:
- Real secrets management
- Auto-updates via systemd timers
- The Docker compatibility layerThis is the guide I wish I had when making the switch.
Read it here: https://blog.hofstede.it/podman-in-production-quadlets-secrets-auto-updates-and-docker-compatibility/
#Podman #Linux #DevOps #Systemd #Homelab #Sysadmin #Containers
@Larvitz this is awesome, thanks for putting it together. I've been using podman for a few years and got started after generating the unit files from running containers. I wish I had a guide like this for getting started.
Quick question if you don't mind; I have a separate container running user and put the unit files in~/.config/systemd/user/instead. You suggest~/.config/containers/systemd/which seems to make sense as a path but I was hoping to understand the difference better. Could you please point me to a resource? -
@Larvitz this is awesome, thanks for putting it together. I've been using podman for a few years and got started after generating the unit files from running containers. I wish I had a guide like this for getting started.
Quick question if you don't mind; I have a separate container running user and put the unit files in~/.config/systemd/user/instead. You suggest~/.config/containers/systemd/which seems to make sense as a path but I was hoping to understand the difference better. Could you please point me to a resource?~/.config/systemd/user/ is for systmd units (podman generate systemd). That was the old way to do it.
~/.config/containers/systemd/ is for Quadlet files, the modern way to describe containers declaratively:
https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html
Quadlets files are similar to Systemd units and describe a container with all it's attributes.
-
@Larvitz been wondering about switching to either podman or libvirt for the plain LXC things I have on a server, because some other admins are not used to it and want GUI tools, but I suppose that means migrating… ?
-
~/.config/systemd/user/ is for systmd units (podman generate systemd). That was the old way to do it.
~/.config/containers/systemd/ is for Quadlet files, the modern way to describe containers declaratively:
https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html
Quadlets files are similar to Systemd units and describe a container with all it's attributes.
@Larvitz ahhhhh perfect, this made it click finally. I was just generically describing how to run an application (happened to be a container) and Quadlets use the unit file approach but describes the container itself (which I read in the unit file but didn't make the connection). Thanks so much!!
-
@oldsysops not sure, I'll have to check that
-
M monkee@chaos.social shared this topic
M monkee@other.li shared this topic