undefined | Better HN

0 pointsINTPenis3y ago0 comments

Yeah I didn't really think before I typed that. If it requires you to install systemd files then it's not really equivalent.

I don't understand why they made it so complicated, if you have a file format just let the user run it from their CWD.

0 comments

bonzini3y ago

Because the idea is that this is a declarative configuration, not something that the user has to run. You first write the configuration, and then running it is just "systemctl start foo".

Generators are the same mechanism by which systemd reads /etc/fstab; just like /etc/fstab entries are treated by systemd as "normal" mount units, systemd will treat .container files just like any other system service.

INTPenisOP3y ago

Yeah but they have invented the declarative file format, but they put it in /etc, why not put it in $HOME/.config/systemd instead? That would make it more on-par with docker compose.

I'm hoping this is in the future of quadlet. Being able to run the files from CWD, using systemd units in $HOME, and not requiring root.

rhatdan3y ago

It works in the home directory. Just place the quadlet file in $HOME/.config/containers/systemd $ systemctl --user daemon-reload $ systemctl --user start QUADLETNAME.service

If you want this to work at boot, you need to do loginctl enable-linger $USERNAME

alexlarsson3y ago

For rootless use, put the files in ~/.config/containers/systemd/

2 more replies

j / k navigate · click thread line to collapse