-
Notifications
You must be signed in to change notification settings - Fork 233
jupyter-dash in a container #16
Comments
I was able to run your example sucessfully by setting debug=False ! BTW I stumbled on the solution because I was getting ConnectionRefusedError: [WinError 10061] No connection could be made because the target machine actively refused it when running the more complex getting_started sample app (with all three ouput modes)! I used your minimal example to troubleshoot and subsequently fixed my error (thank you!) Hopefully this suggestion will help. |
I have JupyterHub running in a docker container that I started with The IP of the host is 10.92.39.100 and I am able to access JupyterHub with The IP inside the container is 172.17.0.4 => Do I need to map an extra port for jupyter-dash, e.g. 8050 or is it possible to access the app over the already mapped port? Edit
I am able to run the dash app. However, the shown link The mode "inline" does not work for the same reason. My workaround is to add an extra cell in Jupyterlab, showing the mapped address:
=> Would be great if I could pass two IPs to jupyter-dash: one for server and one for the target link/inline mode. |
I know this was a while back, and not sure when it was added -- but now you should be able to specify the URL to load from in your create call like:
and then when running still use:
So it runs vs gets loaded at the correct different locations. |
Hi,
I'm trying to prototype a plain-vanilla frontend in Dash for testing my model scoring in a jupyter docker container.
Below my code
Everything starts fine but I get a page with this error
172.23.0.6 took too long to respond.
Any suggestion?
Thanks
The text was updated successfully, but these errors were encountered: