![]() JupyterLab and/or Jupyter Notebook installation.When running Jupyter sessions in containers, such as by using the Kubernetes Job Launcher plugin, you will need to ensure that the image(s) used to launch Jupyter sessions contain, at minimum, the following: To access other folders, create symbolic links to them within the home folder. Only a user’s home folder is visible within Jupyter sessions. Sets the -MappingKernelManager.cull_connected Jupyter setting. Regardless of this setting, only idle (unused) sessions are culled. Whether or not to cull sessions that have a browser connected. Sets the following Jupyter arguments: -NotebookApp.shutdown_no_activity_timeout= -LapApp.shutdown_no_activity_timeout= To disable automatic shutdown, set the value to 0. The amount of idle time to wait in minutes before a Jupyter session is shut down after its kernels and terminals have been culled. Enabling this sets the following Jupyter arguments: -MappingKernelManager.cull_interval=60 -MappingKernelManager.cull_idle_timeout=ġ20, however, it is highly recommend that you set this 0 to disable culling. The amount of idle time to wait in minutes before a Jupyter session’s kernels and terminals are automatically “culled” (shut down). usr/lib/rstudio-server/bin/jupyter-session-runĮnables/disables running of bash profile scripts when starting Jupyter sessions. It is recommended that you do not change this unless you know what you’re doing, and you need to point to a different script. Path to the Jupyter Session launcher executable/script. The default container image to use when launching a containerized Jupyter session.Ĭomma-delimited list of images that may be used for running Jupyter sessions. The default Job Launcher cluster to use when launching a Jupyter session. List of available Job Launcher clusters for launching Jupyter sessions. It is strongly recommended that you do not change this unless you know what you’re doing! Note that this does not override the default value - if you wish to use some of the default arguments, you must contain the default arguments in the configuration value. ![]() Running against multiple different Jupyter versions simultaneously in different Launcher clusters is not supported - they must all be running the same version, or proxying issues will occur.Īrguments to be passed to the Jupyter Notebook command. If Jupyter is being launched via the Launcher and is not installed locally, you are strongly encouraged to set this to the version in use. If set to auto, the version is automatically detected by running the Jupyter Notebook version command. The version of Jupyter Notebook being used. The Jupyter command to run when starting a Notebook session. Using different Jupyter versions for different sessions is not supported.Īrguments to be passed to the Jupyter Lab command. If Jupyter is being launched via the Launcher and is not installed on the Posit Workbench node, must set this to the version in use. If set to auto, the version is automatically detected by running the Jupyter Lab version command on the Posit Workbench node. The Jupyter command to run when starting a Lab session. The following table lists the various configuration options that are available to be specified in the nf configuration file:Įnables launching of JupyterLab sessions.Įnables launching of Jupyter Notebook sessions. Note that this file is not automatically created by Workbench, and must be created before being configured, and the Jupyter feature is disabled by default. Configuration of the Jupyter feature is handled via the config file /etc/rstudio/nf.
0 Comments
Leave a Reply. |