Did quadlet changed the location of the .service units? #26755
Closed
DevDorrejo
started this conversation in
General
Replies: 1 comment
-
https://www.freedesktop.org/software/systemd/man/latest/systemd.generator.html A generator is supposed to put files there, the point is that they are just a temporary service file that gets replaced every time you run systemctl daemon-reload or reboot. The quadlet generator is "enabling" the units by default. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
While working with Quadlet, I found that after creating and generating the
.service
units from.pod
,.container
,.volume
, or.network
files, the resulting service files are stored in:These are ephemeral, auto-generated units created by systemd at runtime. Since they reside under /run, they will disappear after a reboot.
Because of this, these units cannot be enabled permanently using: systemctl --user enable --now .service
at my understand, Instead, the proper way to make them persistent is to keep the .service files in:
It would be right this approach or I am ignoring something?
Beta Was this translation helpful? Give feedback.
All reactions