[Podman] Re: RunRoot & mistaken IDs

On 1/29/24 02:35, lejeczek via Podman wrote: > > > On 28/03/2023 21:00, Chris Evich wrote: >> On 3/28/23 09:06, lejeczek via Podman wrote: >>> I think it might have something to do with the fact >>> that I changed UID for the user >> >> The files under /run/user/$UID are typically managed by >> systemd-logind. I've noticed sometimes there's a delay >> between logging out and the files being cleaned up.  Try >> logging out for a minute or three and see if that fixes it. >> >> Also, if you have lingering enabled for the user, it may >> take a restart of particular the user.slice. >> >> Lastly, I'm not certain, but you (as root) may be able >> to `systemctl reload systemd-logind`.  That's a total >> guess though. >> >> > Those parts seem very clunky - at least in up-to-date > Centos 9 stream - I have removed a user and re/created > that user in IdM and.. > even after full & healthy OS reboot, containers/podman > insist: > > -> $ podman container ls -a > WARN[0000] RunRoot is pointing to a path > (/run/user/2001/containers) which is not writable. Most > likely podman will fail. > Error: default OCI runtime "crun" not found: invalid > argument > > -> $ id > uid=1107400004(podmania) gid=1107400004(podmania) > groups=1107400004(podmania) > context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 > > > Where/what does it persist/insist on that old, > non-existent UID - would anybody know? > > many thanks, L. > _______________________________________________ > Podman mailing list -- podman(a)lists.podman.io > To unsubscribe send an email to podman-leave(a)lists.podman.io Do you have XDG_RUNTIME_DIR pointing at it?