Rootless container quadlet files go under /etc/containers/systemd/users/${UID}/ and the user session will activate the quadlet. If you put it under etc/containers/systemd/users/ then all user sessions will activate the quadlet When starting a container unit, systemd may time out due to the time it takes to pull a container. Use the TimeoutStartSec Service option to extend the default 90 second timeout or pre-pill the image.

podman desktop tutorial https://www.youtube.com/watch?v=YXfA5O5Mr18&t=216s Connecting to remote machine It's still experimental though, and buried in the menus (Settings -> Preferences -> Podman Extension -> Remote (a toggle button). But the GUI seemed to throw js errors until after I had podman remote properly setup on the cli as follows, so only turn it on after the cli works! First, you will need to have your ssh keys already setup correctly to ssh in passwordlessly, and I have read that the ed25519 ssh key algorithm is preferred (YMMV). There are many generate and ssh-copy-id tutorials on the internet. But then you still have to add the remote connection at the command line, and not in the GUI. E.g. `podman --remote system connection add <<NICKNAMEYOURREMOTEMACHINEHERE>> --identity ~/.ssh/id_ed25519 ssh://<<YOURREMOTEUSERNAMEHERE>>@<<YOURIPHERE>>/run/user/<<YOURUIDHERE>>/podman/podman.sock` You should test it at the command-line with something like: podman -c REMOTEMACHINENICKNAME ps Once I sorted through the various connection errors (I initially had the wrong uid & had to upgrade my remote podman to version 4) and got it to work at the cli, I turned it on in the GUI and it worked. I can say the Podman Desktop GUI makes it easier to admin remote podman containers. But there are a few issues I can already see with it, such as it does not not yet visually distinguish between a remote and a local container. Again, it is very early stage... ctop to view metrics So, to work with podman there are some quick steps to set the socket enabled and be transparent with docker-ctop:

In order to support compose, podman needs to expose it’s REST API service through a local UNIX socket. This supports Docker-compatible APIs and native Libpod APIs. Install required packages: - podlet - podman-compose Enable podman-socket:

Introduction to Containers # Take advantage of the native virtualization features available in the Linux kernel. Each container typically encapsulates one self-contained application that includes all dependencies such as library files, configuration files, software binaries, and services. Traditional server/ application deployment:

If you’re used to managing packages installed on VMs, it’s definitely a step up to run containers in podman via quadlet units ansible + podman is pretty close to k8s in terms of overall “how easy is this to manage”-ness, just not in terms of your RTO times or your overall scalability or resiliency