Gotcha, makes sense. Yeah my setup is very straightforward

Agreed. Quadlets and podman are amazing.

I hate docker compose and find that much more complicated. It’s a whole other structure that’s essentially unneeded.

But I started with podman and not docker, so that’s probably why

openSUSE MicroOS is amazing

Just want to chime in here to say I use containerized caddy as a reverse proxy with quadlets and did nothing special.

you got this! don’t give up!

thank you, i will try!

what GPU are you using, btw?

i’m starting to think it’s the debian base of this container image. it may just be too out of date for my GPU.

thanks! that seems in line with what i’m doing, though my container is rootful.

the container is rootful.

any help is appreciated as i’m at a wall. :/

what i’m so surprised about is that it works for owncast, and the setup is the same.

rootful. render group isn’t named in the container and the owncast user isn’t in the group.

but it works, and peertube doesn’t.

thanks! i took a look and sadly i’ve already covered those parts. :/

this is a great thought and i’m not sure, probably not.

when i examine /dev/dri in the container, it has the groupid that it has on host, but not the name. peertube user is not in that group.

i tried making the render group in the container with the same gid and added peertube to it, but it didn’t change anything. this process may not be correct, however, to achieve that goal.

any suggestions for quadlet on how to bring in the render group with peertube in it?

thanks, i just ended up going with a new image with the components installed.

ooo i see. ok i did not consider that

it’s all in the edited op!

well, we can download these libraries from within the container. i just want a way to tell the container to always do that on startup

thank you, i figured it out!

so, actually no change even with setting SELinux to Permissive. so i guees it isn’t SELinux after all…

AMD Radeon RX 7600

6.15.4-1-default

i have not tried that. i’ll give that a go. i ASSUME it’s a selinux permissions issue, but i thought i had that all cleared.