this post was submitted on 12 Feb 2024
6 points (100.0% liked)

Linux Questions

1062 readers
2 users here now

Linux questions Rules (in addition of the Lemmy.zip rules)

Tips for giving and receiving help

Any rule violations will result in disciplinary actions

founded 1 year ago
MODERATORS
6
submitted 9 months ago* (last edited 8 months ago) by possiblylinux127 to c/linuxquestions
 

I have lingering setup and I can still access the container but for what ever reason Podman seems to be unable to access the GPU for no apparent reason.

I think this may be an issue with systemd but I'm not entirely sure.

Solution: you need to be logged in for it to work. I accomplished this on a separate VM with autologin to icewm.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 8 months ago (1 children)

Interesting. For me, it's only the /dev/dri/render* device that is owned by the render group, but this device is world-RW anyway. Still, I guess you can add the user to the render group too? I did find some info that Debian uses that group this way, though I have never used Debian myself, so can't verify that.

[–] possiblylinux127 2 points 8 months ago (1 children)

I already did that so that podman could access the device. (Podman runs as a local user). What was strange was that podman couldn't access it without a graphical session running but my local user could.

[–] [email protected] 1 points 8 months ago

No idea then :( AFAIK the logind mechanism I mentioned originally is based only on permissions, but I had never really needed to look into it further.