add --x-forward
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
it's becoming very standard for many workflows to include running a container with x-forwarding:
I'm proposing a flag --x-forward which basically does:
-e "DISPLAY" -v "/tmp/.X11-unix:/tmp/.X11-unix:rw"
I'm not saying that's the best way to implement. perhaps something like runtime=nvidia-x which would add x in the image and map things etc. Perhaps a --foward-devices or some other way.
But clearly it would massively increase user friendliness and future-proof a lot of documentation on using containers. also it could avoid a lot of people doing xhost + an forgetting about it.
is there any work on this? I'm thinking of all the robotics (ROS) and vision and deep learning (OpenAI gym) as well as games and many other things which are very strong candidates to be packaged as a docker container
Contributor guide
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
The issue names no files, tests, or entry points. Begin by confirming the Docker CLI's existing flag conventions and the proposed DISPLAY and /tmp/.X11-unix mappings; done means an agreed implementation and documented behavior for X forwarding, including whether xhost handling is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100