Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
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:
Pass 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.
No prob! Glad you got it to work, permissions can be a huge pain.