Closed arokem closed 4 years ago
Hi @arokem, sorry I see now the error in the instruction README. That k8s folder is meant for a deployment inside a Kubernetes cluster with jupyter hub. To run the application with Docker, the Dockerfile in the root folder is the one to use.
Thanks @filippomc ! Progress! See #133 for a fix.
Next issue is that http://localhost:8888/geppetto gives me a 404. I noticed in the terminal that I get the following text:
(nwb-explorer) nwb-explorer (master)$docker run -it -p8888:8888 nwb-explorer
[W 19:42:25.421 NotebookApp] Unrecognized alias: '--library=nwb_explorer', it will probably have no effect.
[I 19:42:25.437 NotebookApp] Writing notebook server cookie secret to /home/jovyan/.local/share/jupyter/runtime/notebook_cookie_secret
[W 19:42:25.670 NotebookApp] All authentication is disabled. Anyone who can connect to this server will be able to run code.
[I 19:42:25.995 NotebookApp] Starting Geppetto Jupyter extension
[I 19:42:25.995 NotebookApp] Creating notebook notebook.ipynb
[I 19:42:26.001 NotebookApp] Geppetto Jupyter extension is running!
[I 19:42:26.293 NotebookApp] JupyterLab extension loaded from /opt/conda/lib/python3.7/site-packages/jupyterlab
[I 19:42:26.293 NotebookApp] JupyterLab application directory is /opt/conda/share/jupyter/lab
[I 19:42:26.297 NotebookApp] Serving notebooks from local directory: /home/jovyan/nwb-explorer
[I 19:42:26.297 NotebookApp] The Jupyter Notebook is running at:
[I 19:42:26.297 NotebookApp] http://(e81fa291d87b or 127.0.0.1):8888/
[I 19:42:26.298 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
Which seems good, but when I go to http://127.0.0.1:8888/ I am asked to enter an authentication token and I don't know what the value of this token is (sometimes that appears in the URL, but not in this case; using e81fa291d87b
did not do the trick). I also tried http://e81fa291d87b:8888/, based on the text above, but that didn't work either.
Hi @arokem thanks for your patch! I checked it out and I found there was definitely a problem with packages that were updated since the dockerfile was released. I pushed the fix to the development branch, please let me know if that fixes your problems
Thanks for these tests @arokem. There is an open PR with documentation updates here: https://github.com/MetaCell/nwb-explorer/pull/126/files.
NWBE development/testing will increase a bit in the next few weeks and these and a few other issue should get ironed out. Please do add any other comments/issues you find, and feel free to test any NWB2 files you come across (of reasonable size ~<100MB) on the beta live instance http://nwbexplorer.opensourcebrain.org
Hello! This looks very useful.
I just tried launching this via Docker and wanted to report my experiences:
First, the Dockerfile in the k8s folder is not named
Dockerfile
, so the instructions in the README file do not work as posted. I solved this bymv Dockerfile-hub Dockerfile
, but not sure whether that is what is causing my other troubles.Which brings me to the main issue I encountered, which is that I get: