Mirantis / Mirantis/cri-dockerd
device_ownership_from_security_context = true Is this supported ?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 356
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 3
Description
Expected Behavior
CRIO./containerd implements device_ownership_from_security_context = true
where the device mounts follows the security context declared in the POD spec
Actual Behavior
Cri-dockerd / docker doesnt honor the pwermissions of devices to that of the user
Steps to Reproduce the Problem
Specifications
- Version: 0.3.0
- Platform: RockyLinux
- Subsystem: docker-26
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.
Research direction
Start by reviewing how cri-dockerd version 0.3.0 handles device ownership from a Kubernetes Pod security context when using Docker 26 on Rocky Linux, and compare it with the stated CRI-O/containerd behavior. Reproduce the issue with a concrete Pod specification and device-permission check; done means the support status and observed behavior are documented or the discrepancy is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100