Quadlet are not working exactly as in the documentation in my system, should I open an issue?

[a40yostudent]

I tried what I found on the documentation about Quadlets so I put this in .config/containers/systemd/npm.network

# npm.network
[Network]
Driver=bridge
Gateway=10.89.0.1
IPAMDriver=host-local
PodmanArgs=--interface-name npm
Subnet=10.89.0.0/24

[Install]
WantedBy=default.target

but then after running systemctl --user daemon-reload the service could not be found.

Instead, running /usr/libexec/podman/quadlet --user .config/containers/systemd/ -v works as intended, and then systemctl --user start npm-network.service actually does the job.

What's happening here and why the standard documentation could not help in my case? I'm doing this on a Fedora 41 Server.

[ygalblum]

I just did the same and it worked for me with systemctl --user daemon-reload.

Furthermore, running /usr/libexec/podman/quadlet --user .config/containers/systemd/ -v as you did does not produce the service unit at a place that systemd looks at since the the argument you passed .config/containers/systemd/ is the destination directory.

Please recheck whether systemctl --user daemon-reload didn't actually do the work. Please note that I sometimes autocompletion does not work immediately after it (in case you are relying on it)

[a40yostudent]

here are the paths I can find with systemctl --user show:

10:45:44 a40yostudent@localhost ~ → systemctl --user show pihole.service | grep Path
FragmentPath=/run/user/1000/systemd/generator/pihole.service
SourcePath=/home/a40yostudent/.config/containers/systemd/pihole.container
DropInPaths=/usr/lib/systemd/user/service.d/10-timeout-abort.conf
10:45:51 a40yostudent@localhost ~ → systemctl --user show gitea.service | grep Path
FragmentPath=/run/user/1000/systemd/generator/gitea.service
SourcePath=/home/a40yostudent/.config/containers/systemd/gitea.container
DropInPaths=/usr/lib/systemd/user/service.d/10-timeout-abort.conf       
10:47:09 a40yostudent@localhost ~ → systemctl --user show npm-network.service | grep Path
FragmentPath=/run/user/1000/systemd/generator/npm-network.service
SourcePath=/home/a40yostudent/.config/containers/systemd/npm.network
DropInPaths=/usr/lib/systemd/user/service.d/10-timeout-abort.conf
10:47:26 a40yostudent@localhost ~ → systemctl --user show npm.service | grep Path
FragmentPath=/run/user/1000/systemd/generator/npm.service
SourcePath=/home/a40yostudent/.config/containers/systemd/npm.container
DropInPaths=/usr/lib/systemd/user/service.d/10-timeout-abort.conf

is /run/user/1000/systemd/generator/*.service a fair location for daemon reload?

[ygalblum]

Yes, the generated unit files are stored under $XDG_RUNTIME_DIR/systemd/generator/*.service.

I can see this:

10:47:09 a40yostudent@localhost ~ → systemctl --user show npm-network.service | grep Path
FragmentPath=/run/user/1000/systemd/generator/npm-network.service
SourcePath=/home/a40yostudent/.config/containers/systemd/npm.network

So, the service unit file for the network is created as expected