Additional support re: non-udev-managed devices
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, linux, rust
- Domain
- devops, infrastructure
Research direction
Start by reviewing how container-hotplug discovers udev-managed devices and passes them into Docker containers. Determine where static or non-udev device nodes could be configured, including the listed NVIDIA character-device major and minor numbers; done requires a decided scope and a way to verify those devices are available in the container.
Written by the indexing model from the issue text.
Description
Is there a way to pass non-udev-managed devices into a container? For examples, the NVIDIA kernel driver writes these devices (which aren't monitored via udev, therefore the container doesn't start as udev cannot find them under DEVNAME):
crw-rw-rw- 1 root root 195, 0 Oct 20 13:36 /dev/nvidia0
crw-rw-rw- 1 root root 195, 1 Oct 20 13:36 /dev/nvidia1
crw-rw-rw- 1 root root 195, 255 Oct 20 13:36 /dev/nvidiactl
crw-rw-rw- 1 root root 507, 0 Oct 20 13:34 /dev/nvidia-uvm
crw-rw-rw- 1 root root 507, 1 Oct 20 13:34 /dev/nvidia-uvm-tools
/dev/nvidia-caps:
total 0
cr-------- 1 root root 234, 1 Oct 20 13:36 nvidia-cap1
cr--r--r-- 1 root root 234, 2 Oct 20 13:36 nvidia-cap2
Char nodes 195:(0/1/255) 507(0/1) and 234(1/2).
Please let me know if this request (to allow static/non-udev device nodes) is considered in-scope for this project,
Thank you!
- Dominant language
- Rust
- Stars
- 16
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lowRISC/container-hotplug
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
lowRISC/container-hotplug#11 · 1 comment ·
All issues in lowRISC/container-hotplug
Similar issues
-
Browser (wasm) relay client cannot connect to relays whose URL has a trailing-dot FQDN hostname Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
n0-computer/iroh#4550 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
paritytech/zombienet-sdk#591 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
farion1231/cc-switch#7638 · 1 comment ·
-
onnx-ir re-exports ModelProto and GraphProto but not NodeProto, AttributeProto and AttributeType Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100