Hi guys. Trying "regular" podman generated systemd service unit with systemd fails with also what I could have fiddled into it so I wonder - if a rootless container, created and managed by a non-root user can be given to systemd(system's, not user's) for complete management?

many thanks, L. _______________________________________________ Podman mailing list -- podman(a)lists.podman.io To unsubscribe send an email to podman-leave(a)lists.podman.io

On 25/05/2021 08:45, Valentin Rothberg wrote: > Hi, > > Thanks for reaching out. > > On Fri, May 21, 2021 at 7:50 PM lejeczek via Podman > <podman(a)lists.podman.io <mailto:podman@lists.podman.io>> > wrote: > > Hi guys. > > Trying "regular" podman generated systemd service unit > with > systemd fails with also what I could have fiddled into > it so > I wonder - if a rootless container, created and > managed by a > non-root user can be given to systemd(system's, not > user's) > for complete management? > > > I have a hard time brain-parsing the question. Can you > rephrase the question (and ideally share a reproducer)? > > Are you attempting to run a systemd /system/ unit with the > User=... field? Short answer - yes. a) You have your systemd service definition generated by a non-root(and container also in whole "belongs" to that user) b) Now you want system's sytemd(not user's) to have it to manage(from /etc/systemd/ .. system or user, whichever would/should work)

thanks, L. > > Kind regards, > Valentin > > many thanks, L. > > _______________________________________________ > Podman mailing list -- podman(a)lists.podman.io > <mailto:podman@lists.podman.io> > To unsubscribe send an email to > podman-leave(a)lists.podman.io > <mailto:podman-leave@lists.podman.io> > _______________________________________________ Podman mailing list -- podman(a)lists.podman.io To unsubscribe send an email to podman-leave(a)lists.podman.io