Solved!
more expanded details can be seen here:
Thank you, all!
hey all!
i need some guidance. can you help point me in the right direction?
there a docker image that is basically fine, except i just want to add a group to it so that group will exist in the container.
how do i do this? is there a way to do this that will just pull the original image as is, so it will update when the original image updates, and then just add the group i need?
thanks in advance!
What exactly are you doing? You may not need to do this. I know you can use the group number instead of the name if it doesn’t exist in some cases.
for the expanded discussion, you can check here:
https://github.com/TheoLeCalvar/peertube-plugin-hardware-transcode-vaapi/issues/6#issuecomment-3246562059
Right, you just need to make sure that the user inside the container has permission to the device. They cover this in the front page of the repo: https://github.com/TheoLeCalvar/peertube-plugin-hardware-transcode-vaapi?tab=readme-ov-file#running-the-docker-image
And you can map internal users to external users. This isn’t as common with Docker since things tend to run as root, so maybe look up Podman docs where it’s more common since it’s whole schtick is running with minimal permissions.
this would be useful but i was never able to figure out how. :/
Basically this:
docker run -it --user $UID:$GIDPass it a user and group that have the appropriate access, and no more. You can also set this in Docker compose or whatever other abstraction you’re using.
so, in this case, the internal user is peertube with UID 999.
would i then use that UID, and the GID of the passed render device?
Passing that in basically overrides the [USER field in the Dockerfile](docker run -it --user $UID:$GID). Make sure that user/group combo has access to the render device.
lol i can’t believe this just worked. XD
falls over i’ve spent MONTHS on this. XD i am LITERALLY completely embarrassed now. XD
i just didn’t think i had that level of control. i kept reading that even if the IDs match it’s not REALLY the same as the host permissions, but this worked just fine. a much simpler solution.
well, thank you for that! still so much to learn.
right, so what confused me is that the basic setup works for owncast, but the same setup not for peertube.