You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After that it seemingly stops. When I open the taskmanager I can see, that the task "vmmem" is constantly working (4%CPU) and using more and more memory. Just until I press CTRL+C. Then it continues with starting the notebook
^C[I 05:52:35.198 NotebookApp] Writing notebook server cookie secret to /home/wradlib/.local/share/jupyter/runtime/notebook_cookie_secret
[W 05:52:35.641 NotebookApp] WARNING: The notebook server is listening on all IP addresses and not using encryption. This is not recommended.
[I 05:52:35.668 NotebookApp] Loading IPython parallel extension
...
I have Windows 10 with WSL2 activated/deactivated (tried both). Docker Engine v19.03.13 (latest). Kubernetes deactivated.
The text was updated successfully, but these errors were encountered:
I forgot to post my command. It is: docker run -ti --rm --name wradlib_nb -p 8888:8888 -v C:\path\to\docker\wradlib\wradlib-notebooks:/home/notebooks -v C:\path\to\docker\wradlib\wradlib-data:/home/wradlib-data -e LOCAL_USER_ID=$UID -e WRADLIB_DATA=/home/wradlib-data wradlib/wradlib-docker:master-full /opt/conda/envs/wradlib/bin/jupyter notebook --notebook-dir=/home/notebooks --ip='*' --port=8888
@Scentyoo Thanks for reporting this! Currently I've no idea what causes this behaviour. Unfortunately I can't try to reproduce this, I've no windows machine to try out. If you find anything to fix this, please let us know.
When I start the container the following lines are printed:
After that it seemingly stops. When I open the taskmanager I can see, that the task "vmmem" is constantly working (4%CPU) and using more and more memory. Just until I press CTRL+C. Then it continues with starting the notebook
I have Windows 10 with WSL2 activated/deactivated (tried both). Docker Engine v19.03.13 (latest). Kubernetes deactivated.
The text was updated successfully, but these errors were encountered: