Comment

frongt@lemmy.zip ⁨1⁩ ⁨month⁩ ago

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: github.com/…/peertube-plugin-hardware-transcode-v…

Sort:hotnew top

sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨month⁩ ago
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.

source
- nico198X@piefed.europe.pub ⁨1⁩ ⁨month⁩ ago
  this would be useful but i was never able to figure out how. :/
  
  source
  - sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨month⁩ ago
    Basically this:
    
    docker run -it --user $UID:$GID
    
    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.
    
    source
    nico198X@piefed.europe.pub ⁨1⁩ ⁨month⁩ ago
    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?
    
    source
    -> View More Comments
nico198X@piefed.europe.pub ⁨1⁩ ⁨month⁩ ago
right, so what confused me is that the basic setup works for owncast, but the same setup not for peertube.

source