Self Hosted - Self-hosting your services.

506 readers

2 users here now

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

No harassment
crossposts from c/Open Source & c/docker & related may be allowed, depending on context
Video Promoting is allowed if is within the topic.
No spamming.
Stay friendly.
Follow the lemmy.ml instance rules.
Tag your post. (Read under)

Important

Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!

Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.

Cross-posting

!everything_git@lemmy.ml is allowed!
!docker@lemmy.ml is allowed!
!portainer@lemmy.ml is allowed!
!fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
!selfhosted@lemmy.ml is allowed!

If you see a rule-breaker please DM the mods!

founded 3 years ago

MODERATORS

Zoe8338@lemmy.ml

dogmuffins@lemmy.ml

testman@lemmy.ml

Podman rootless Plex with H/W transcoding? (lemmy.nine-hells.net)

submitted 1 year ago by falcon15500@lemmy.nine-hells.net to c/selfhost@lemmy.ml

3 comments fedilink hide all child comments

cross-posted from: https://lemmy.nine-hells.net/post/56646

Hi all - recently moved my old docker setup across to Podman rootless containers, however I am having some trouble with getting my Plex container to use the on CPU hardware transcoding.

"/dev/dri" device is being passed into the container and after reading, I also added "--group-add=keep-groups" to my configuration.

Still no luck getting the "video" group to the plex user inside the container so it can access the device.

Anyone successfully running rootless Plex with H/W transcode?

you are viewing a single comment's thread
view the rest of the comments

[–] alex@agora.nop.chat 1 points 1 year ago

OK, looks like my setup isn't any different to yours, except that I have --security-opt=label=disable set too. The reason for this is because of this issue, which should be fixed by now. Your version may be too old?

If you get the same result from ausearch as on that issue, you may be seeing the same problem.