Tecnativa / Tecnativa/docker-socket-proxy
GPU Restriction Not Propagated in Docker-in-Docker (DinD)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.8k
- Forks
- 207
- PR merge metrics
- No merged PRs in 30d
Description
I have a container running with the Docker socket (docker.sock) mounted, and I set CUDA_VISIBLE_DEVICES=0 to restrict it to a single GPU. However, when I create another container inside this first one (Docker-in-Docker), the inner container has access to all GPUs and all containers on the host.
I would like to know if it is possible to use docker-socket-proxy to restrict GPU access for containers created inside the DinD environment.
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
No files, tests, or entry points are identified in the issue. Start by checking how Docker-in-Docker container-creation requests and GPU/device restrictions are exposed through the proxy, then determine whether the requested restriction is supported. Done means providing a verified feasibility answer or a clearly scoped implementation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100