Today I learned: I don't need to put all my quadlets flat into containers/systemd, I can split them into subdirs 🎉.

That makes manually managing the ~50 containers (+volumes and networks) on my home server much clearer.

#podman #coreos #fedora #systemd

@moreentropy interesting, and useful, find. I wonder if this is intended. The only mention I could find in podman-systemd.unit(5) was about user units:
For unit files placed in subdirectories within /etc/containers/systemd/user/${UID}/ and the other user unit search paths, Quadlet will recursively search and run the unit files present in these subdirectories.
#podman #podmanquadlets #SystemD
@mskoett That's actually the part of the manpage I read before trying this, but you're right this explicitly only mentions 'the other *user* unit search paths', so it's not documented (in that man page) for rootful containers.

@moreentropy @mskoett Cool, it's also working for rootless podman Quadlets configured on user level.
Would be a good thing to clean up the directory structure before the number of containers is increasing.

Thanks for finding and sharing this "feature"!

#linux #systemd #podman #quadlets

@moreentropy @mskoett Addition: subdirs named with trailing ".d" holding rootless quadlets in .config/containers/systemd are not recognized.

Wanted to restructure my quadlets in subdirs named with trailing ".d" similar to subdirs in /etc/systemd/system does not work.
Using trailing ".dir" would work, but I think then I will use subdir names without any trailing "." name part.

@db_geek I would assume that ".d" subdirs don't work because quadlet uses ".d" directories to support the same drop-in logic systemd uses.
@moreentropy Thank you, that makes sense.
I thought it would be nice naming my quadlet subdirectories with a trailing ".d".
But that's okay, the restructuring into subdirectories alone is already great for a better overview.