Help Center/ ModelArts/ Troubleshooting/ DevEnviron/ Custom Image Faults/ Faults of Custom Images on Notebook Instances
Updated on 2025-11-18 GMT+08:00
View PDF
Share

Faults of Custom Images on Notebook Instances

If an error occurs when using a custom image, the possible causes are as follows:

  • The custom image does not belong to user ma-user or user group ma-group.
  • The /home/ma-user directory that stores the custom image does not belong to user ma-user or user group ma-group.
  • The directory permissions of /home/ma-user must be set to 750 for the custom image.
  • The created custom image cannot run properly by running the docker run command in the local host.
  • The fault may be caused by the installation of JupyterLab. In this case, run commands in local JupyterLab to list related static file paths, and delete and uninstall JupyterLab.
  • The user service uses ports 8888 and 8889 of the official development environment. In this case, modify the process port number.
  • PYTHONPATH and sys.path are specified by the user image. In this case, the fault is caused by the service startup invoking conflict. You need to start the instance before specifying PYTHONPATH and sys.path.
  • The dedicated resource pool with SUDO permissions is enabled, while SUDO is not installed or installed incorrectly.
  • The used cann and CUDA environments are not compatible.
  • The Docker image configuration is wrong, or there is a network or firewall block, or problems with file permissions, missing dependencies, or build commands.
  • Check whether the following problems occur in the Anaconda environment:
    • An invalid directory, like pythonNone, exists in the {python_env}/lib folder. It should be named python plus the version number, such as python3.7. This might happen due to wrong environment setup or accidental actions.
    • You might have created an empty folder in the Anaconda environment directory {conda}/envs or created an invalid folder in the environment's lib directory. This can break the Anaconda directory structure.
    • You might have deleted necessary files in an environment directory. This can stop the Anaconda environment from working correctly.
  • For details about SSH troubleshooting, see Accessing a Notebook Instance Using SSH for Troubleshooting.
Parent topic: Custom Image Faults