Solved!

more expanded details can be seen here:

https://github.com/TheoLeCalvar/peertube-plugin-hardware-transcode-vaapi/issues/6#issuecomment-3246562059

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!

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 days 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.

      • Nico198X@piefed.europe.pubOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 days 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?

        • sugar_in_your_tea@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          3
          ·
          2 days ago

          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.

          • Nico198X@piefed.europe.pubOP
            link
            fedilink
            English
            arrow-up
            3
            ·
            edit-2
            2 days ago

            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.