-
Notifications
You must be signed in to change notification settings - Fork 233
Can’t run JupyterDash or Plotly from JupyterLab (3.0.10) with docker container. #57
Comments
I'm also struggling to get Jupyter Dash working consistently from within a docker container setup. Note Plotly and other libraries/extensions work perfectly so i'm not sure why you are having issues there. Is there any guide / recommended approach for using jupyter dash in a docker environment? If it matters i'm running on a synology nas. My dockerfile is:
My requirements.txt file is:
My docker-compose file is:
I have a reverse proxy to access this via a subdomain - python.domain.com. An example dash app is:
I'd been experimenting with different combinations to try to get it working. If I start the dash by specifying the host - app.run_server(host='0.0.0.0') - it sometimes works and I can access the dash by going to the ip address of my nas and port 8050. However sometimes i get an error saying the port is in use, despite it not being in use. I'd like to get it working within the jupyter environment, however i get a similar error (127.0.0.1 not found). If anyone has any tips or suggestions it would be highly appreciated. |
Same here. jupyter-dash==0.4.0 seems not to play with the latest JupyterLab 3.1.7 nicely. |
I imagine a pre-build extension would help here #49 |
When I tried to use JupyterDash from the JupyterLab (3.0.10) docker container, I got the error that the webserver is not responding:
My docker file:
Docker build command:
Docker run command:
I got the error described above, trying to run getting_started.ipynb from this repo.
Should I call JupyterDash.infer_jupyter_proxy_config() when I run notebook in container?
Another issue with this setup. If I try to use plotly, it's plots nothing, without error, just blank area after running cell.
My code snippets:
or
The text was updated successfully, but these errors were encountered: