Some applications expect a home directory for the user in order to save and read configuration files, so if you attempt to use them without such a directory existing in the container's filesystem, you may receive warnings or errors. volume="/etc/sudoers.d:/etc/sudoers.d:ro" \ Log in with your uid:gid and add some shared volumes to be able to really use your local account in the container docker run -it \ some applications need a home directory - since you have no name you won't a have a home directory.your user is not named - you won't be able to change anything in the container and.This involves mounting additional directories and becoming yourself in the container: This will add the container's hostname to the local family's list of permitted names.Īnother way is to use your own user's credentials to access the display server.
Xhost +local:`docker inspect -format='' $containerId` The first is to runĪfter you are finished using the containerized GUI, this will return the access controls that were disabled with the previous command.Ī better option is opening up xhost only to the specific system that you want, for instance if you are running a container on the local host's docker daemon with container's ID stored to the shell variable containerId If you are concerned about this (as you should be), you have at least two options. Xhost +local:root # for the lazy and reckless So with a little effort, someone could display something on your screen, capture user input, in addition to making it easier to exploit other vulnerabilities that might exist in X. This is not the safest way however, as you then compromise the access control to X server on your host. We can then adjust the permissions the X server host. This will fail at first and look something like this, but that's ok: volume="/tmp/.X11-unix:/tmp/.X11-unix:rw" \Ībove, we made the container's processes interactive, forwarded our DISPLAY environment variable, mounted a volume for the X11 unix socket, and recorded the container's ID. The simple way is expose your xhost so that container can render to the correct display by reading and writing though the X11 unix socket. The fourth is isolated, works remotely, but is slow.
VNC VIEWER FOR MAC DOCKER PORTABLE
VNC VIEWER FOR MAC DOCKER DRIVER
If you have an nvidia driver and need graphics acceleration you can run it with -x11 as an option to enable the X server in the container. Rocker is a tools which will help you run docker containers with hardware acceleration.
0 kommentar(er)
