133
submitted 2 days ago by [email protected] to c/[email protected]
you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 4 points 2 days ago* (last edited 2 days ago)

Not true. I run them rootless on my server as we speak. :)

[-] [email protected] 1 points 1 day ago

How do you do that? Please link a description. This has been a major stumbling block for me

[-] [email protected] 1 points 1 day ago* (last edited 1 day ago)

Are you placing your service files in ~/.config/containers/systemd of the home dir of the user you want them to run as?

Here is a link: https://linuxconfig.org/how-to-run-podman-containers-under-systemd-with-quadlet

[-] [email protected] 1 points 1 day ago

Yeah, that works, but it means the services cannot be managed by systemctl as root anymore. Or am I missing something?

[-] [email protected] 2 points 1 day ago* (last edited 1 day ago)

You can if you want to. But I don’t think that is best practice. The idea of quadlets is the bring Linux norms to containers. You contain and manage all permissions for that container in that user.

I personally have completely separated users and selinux mls contexts for each container group (formerly docker compose file) and I manage them thusly. It’s more annoying but it substantially more secure.

This being said I think you can do it as root. I think this might work but I am not certain sudo systemctl --user -M theuser@ status myunit.service

[-] [email protected] 3 points 2 days ago

Same here; Rootless Podman Quadlets gang unite (there is two of us in total)

[-] [email protected] 3 points 2 days ago
this post was submitted on 09 Jul 2025
133 points (84.8% liked)

Linux

8376 readers
353 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of [email protected] and The GIMP

founded 2 years ago
MODERATORS