Help Center/ ModelArts/ Image Management/ Using Custom Images in Notebook Instances/ Troubleshooting for Custom Images in Notebook Instances
Updated on 2024-06-21 GMT+08:00
View PDF
Share

Troubleshooting for Custom Images in Notebook Instances

If a fault occurs when using your custom image, check the symptom by referring to the following:

  • 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.
  • If the remote SSH is used, the OpenSSH muster be compatible with or later than 8.0
  • 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 incorrect, there is a restriction on network and firewall, or the image is incorrectly created (file permissions, dependencies, and build commands).