Guide to fix custom user-installed environments missing from notebook kernel selection

Announcements
,
1

A recent change to Fornax means that any custom environments you created using the setup-pip-env or setup-conda-env tools may be missing from the list of kernels you can choose from when creating or running a notebook.

This post will guide you through an easy fix:

  1. Open a terminal from the Fornax launcher.
  2. Run cd to ensure that you’re in your home directory (if you are using an existing terminal session).
  3. Run cp -r .local/share/jupyter/kernels /scratch/.jupyter (to copy existing kernel definitions to the new location used by Fornax).
  4. Refresh your browser, and your custom environments should be available again in the ‘Notebook’ and ‘Console’ sections of the Fornax launcher, and in the kernel selection drop down of notebooks.

This fix will persist across Fornax sessions, so you only need to go through this process once, and any new custom environments that you set up will be available for use as notebook kernels as usual.

Please post in the helpdesk category if you have any issues, and we’ll be happy to provide support!