-
Notifications
You must be signed in to change notification settings - Fork 106
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
Desktop not working in Docker build #47
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
This is a log produced inside the container
|
|
I have the same problem and removing the changes from commit |
This issue affects both. |
Ok, I don't know the exact details of the interaction of jupyterhub with the containers, so I thought it may provide this |
Correct. |
@benz0li Using a fixed port is fine when jupyterhub launches containerized (or partially namespaced) single user environments, but it causes problems when jupyterhub-launched servers are running unnamespaced on shared systems, e.g. The Littlest JupyterHub. (That in itself is a security issue if proxied services don't have any security or auth measures in place.) So jupyter-remote-desktop would be compatible with more jupyterhub deployments if the port assignment was dynamic. |
@domna you need to pass |
This does not solve the problem: docker run -it --rm --security-opt seccomp=unconfined -p 8888:8888 jupyterlab/qgis/base:3.32.2
I have changed https://github.com/b-data/jupyterlab-qgis-docker-stack/blob/59091f1bd17c26cb634fd5f05469611db6aa2dc2/base/Dockerfile#L372 from |
Reverting 447bf86 results in (omitting extensive logs)
Omitting the display number for TurboVNC is not the problem. Not setting the port seems to be it. |
It works on the second attempt: docker run -it --rm -p 8888:8888 quay.io/jupyter-remote-desktop-proxy/base Opening desktop the first time:
Opening desktop the second time:
|
@yuvipanda But yes, it works. Although your image is using TigerVNC whereas mine has TurboVNC installed. I will do further testing and also try with TigerVNC. |
The changes introduces in 447bf86 work with TigerVNC but not TurboVNC. @yuvipanda Please close in favour of issue #54. |
Bug description
Remote desktop running on a remote server and port forwarded to a local desktop starts, but clicking Desktop gives an error and the desktop does not start.
Expected behaviour
Clicking the desktop icon opens a remote desktop.
Actual behaviour
How to reproduce
On a remote server:
docker build -t jupyter-remote-desktop-proxy .
docker run --rm -p 8888:8888 jupyter-remote-desktop-proxy
Locally:
Your personal set up
Server:
Local: OSX 13.4 Ventura
Full environment
Configuration
# jupyterhub_config.py
Logs
The text was updated successfully, but these errors were encountered: