-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to pass extra options do Docker? #332
Comments
Dear @chlohr, Thank you for opening this issue! Currently, directly passing extra options to Docker is not supported. However, we are actively exploring the possibility of adding support for mounting additional volumes on devices in the upcoming releases. Could you please share more details about your specific use case? This will help us understand your requirements better and potentially find a suitable solution using the currently available features. Thanks! |
Hello, The simplest and lightest way to do this is to share the unix socket /tmp/.X11-unix/X0 from the user's session on the host machine towards the containers. Of course, there are then a few details to adjust ('export DISPLAY=:0' in containers, and 'xhost +SI:localuser:$USER' on the host). This is why I would be interested in ways to pass such extra mounting option to docker. For now, my workaround is to put this unix socket in the /shared/ folder (with symlink to /tmp/.X11-unix/X0), and having a forwarding process in the host Another alternative is to do X11 via TCP ('export DISPLAY=172.17.0.1:0'), and a forwarder A final alternative is to ssh -X from the host, which requires finding the binded IP addresses of the nodes. But all these alternatives are complicated. I'd rather just share the X11 unix socket as mentioned at the beginning. Regards |
Related Bug
Hi,
Is there some way to pass extra options (or volumes) to Docker?
(I would have been interested in mounting /tmp/.X11-unix/X0 ;-) )
Best regards
Feature Description
Offering some ways for a GUI would be a plus.
Solution
No response
Alternative Solutions
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: