dangeroustech / dangeroustech/StreamDL

feat(qsv): document and expose Intel /dev/dri device passthrough

Open
#605 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
19
Forks
0
Avg merge
29m
Merged PRs (30d)
1

Description

Goal

Opt-in Docker Compose / docs so operators can pass /dev/dri (Intel Quick Sync / VAAPI render node) into the StreamDL client container.

Context

Parent epic: #452

This is Phase 1 of Quick Sync support. Device passthrough alone does not enable QSV with the current mwader/static-ffmpeg client image — that lands in the Phase 2 follow-up. This issue only makes the ops surface honest and ready.

Scope

  • Extend docker-compose.yml.example with a commented, opt-in devices: (+ optional group_add for video/render) on the client service
  • README: host prerequisites (/dev/dri/renderD*), finding GIDs, PUID/PGID interaction, and clear note that a QSV-capable FFmpeg is still required (Phase 2)
  • No Dockerfile / default behavior change

Out of scope

  • QSV-capable FFmpeg image (Phase 2)
  • First-class FFMPEG_HWACCEL knobs (Phase 3)
  • NVIDIA / AMD

Depends on

  • None (first slice of #452)

Blocks

  • Phase 2 QSV client image work
  • Phase 3 hwaccel presets (practically needs device + capable FFmpeg)

Acceptance

  • Compose example documents opt-in /dev/dri passthrough
  • README covers host setup and limitations with static FFmpeg
  • Default install path unchanged (no required devices)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with docker-compose.yml.example and locate the client service, then review the README’s existing container and permissions guidance. Document opt-in /dev/dri passthrough, relevant video/render GIDs, PUID/PGID interaction, and the static FFmpeg limitation; verify the default install path remains unchanged and all acceptance items are covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose
Domain
devops, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
76/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.