-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[BUG] - Startup issues with low CPU allocation #1771
Comments
Why do you think tornado and nest-asyncio fixes the issue? |
It does not fix the issue, but it makes it much less common. Only a couple of percent of launches will fail after using the versions specified. This is the simplest reproducible case that I could create for this issue. Is it something that you can also reproduce? I believe it is probably related to the following issue jupyterlab/jupyterlab#11934 |
There seems to be a PR for this issue already. |
Thank you @Bidek56. |
@minrk @blink1073 @kevin-bates could you please take a look here (and maybe to the attached PR)? |
We're are going to remove the use of |
Great news @blink1073, thank you! We will be waiting for release then. |
Upstream issue was resolved, and the latest |
What docker image(s) are you using?
base-notebook
OS system and architecture running docker image
linux/amd64
What Docker command are you running?
docker run -v $PWD:/home/jovyan -p 8888:8888 --memory=1000m --cpus=0.5 jupyter/base-notebook:lab-3.4.4
How to Reproduce the problem?
Command output
Expected behavior
Workspace with multiple notebooks running as was the case before the container was restarted.
Actual behavior
Environment is unusable. None of the kernels start the second time.
Anything else?
Issues seems to be resolved with the following modifications to the base image. Best tested with a new bind mount volume.
The text was updated successfully, but these errors were encountered: