Help Center/
ModelArts/
Troubleshooting/
DevEnviron/
Save an Image Failures/
No Kernel Is Displayed After a Notebook Instance Created Using a Custom Image Is Started
Updated on 2024-12-30 GMT+08:00
No Kernel Is Displayed After a Notebook Instance Created Using a Custom Image Is Started
Symptom
After an instance created using a custom image is started, no kernel is available when a user opens JupyterLab to create a notebook instance.
Possible Causes
The Python environment of the custom image is not registered.
Solution
- Run the following command on the Terminal to check the number of Conda environments of the instance:
conda env list
- Run the following commands to switch to the corresponding environment and check whether the ipykernel package exists:
conda activate base # Replace base with the actual Python environment. pip show ipykernel
- If ipykernel does not exist in the Conda environment, add a custom IPython kernel in a notebook instance and install it.
Parent topic: Save an Image Failures
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot