-
Notifications
You must be signed in to change notification settings - Fork 221
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
Unable to connect kernel #1333
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
Could be this? enterprise_gateway/pyproject.toml Line 29 in 9424e3f
|
Correct. EG doesn't support jupyter_client 7 or higher, nor does it support jupyter_server 2 or higher. If you must use server >= 2 and client >= 7 you may want to explore using gateway_provisioners. If you need your "kernel server" separated from your notebook server, you could deploy kernel gateway with gateway provisioners to get similar functionality. That said, EG should be usable so long as your python environments are properly configured. |
@kevin-bates and @lresende - Thank you for your information. Below is my setup
Are you saying that I should use the same versions of jupyter-server and jupyter_client as JEG pinned to? i.e 6.1.12 and 1.24.0. Please, clarify it? If possibel, please share requirements.txt file? Yes, I tried to use JEG on k8s (AWS-EKS) and Jupyter-server/lab from the laptop/EC2 box but I ran into the same above issues.
I will test your suggestions and keep posted. Thanks again for your help. |
I was able to make it work using JupyterLab==3.6.5 with jupyter-client==6.1.12 and jupyter-server==1.24.0 same as JEG 3.2.2. Below is the details configuration.
Next, I will try suggested using kernel gateway with gateway provisioners. Is there an ETA for JEG supports kernel provisioners? |
Not really (unfortunately), unless someone wants to take that on. Although not required, it would be good to first move the base Jupyter Server to 2.0 prior to removing the process-proxies, but given the authorization hurdles encountered in a similar exercise in JKG, it might be better treat the two tasks independently. (Although if the goal is to have a combined Python env for both server and EG, we'd need JS 2.x. I don't view the combined envs to be a requirement since the whole purpose of EG is to separate the compute (kernels) from the user's desktop - and you can achieve that today using JKG and GatewayProvisioners.) |
Description
Jupyter Enterprise Gateway 3.2.2
Python 3.9.16 using virtual environment
Using single server deployment to validate JEG with jupyter Lab (running another venv terminal) but no success with it.
Please, let me know how to fix this issue. I appreciate your help in advance.
Jupyter server and lab details
The text was updated successfully, but these errors were encountered: