-
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] - Server connection error #1800
Comments
I ran the same command on my Ubuntu 22.04 VM and it seems to work - so this issue is probably related to your specific host machine.
I guess this might be the problem. Do you have the system packages upgraded? |
Also, I see many jupyter labs are launched simultaneously:
Could you try using |
Thank you !
I don't know.
I am not sure about what system packages are.
I do not want to stops all my containers, I have ML models in training ;-) . I tried without @mathbunnyru , since it works on your machine, you probably can close the issue? |
Let's keep it open for a while. Maybe someone had a similar problem and found the solution. |
Can confirm the same issue with the following setup:
|
UPDATE: Upgrading to the newest version of Docker (20.10.18) seems to resolve the issue in my case |
Thank you @lacic, that's great news! |
I think this can be considered solved, so closing this issue. |
Can confirm, Ubuntu 22.04, upgrading docker-ce from |
What docker image(s) are you using?
minimal-notebook
OS system and architecture running docker image
Pop!_OS 20.10
What Docker command are you running?
docker run --pull=always --network host jupyter/minimal-notebook
How to Reproduce the problem?
Command output
Expected behavior
Open a working jupyterlab
Actual behavior
And the container is stopped (last line is
Writing notebook-signing key to /home/jovyan/.local/share/jupyter/notebook_secret Operation not permitted (src/thread.cpp:269)
Anything else?
If I run an older image, the problem is not present.
docker run --rm --pull=always --network host jupyter/minimal-notebook:2022-05-28
My system is a bit old (2 years old), the cause of the problem could be linked to that ?
My docker version is also a bit old:
The text was updated successfully, but these errors were encountered: