Setting diagnostics.enabled: true produces a segfault error in the pod logs:
2024-01-31T13:40:58.692978Z [rserver] INFO Server: RStudio - stats monitor reporting interval: 60s
Job launcher configured with the following clusters: Kubernetes
launcher-adhoc-clusters is empty - all clusters may be used to launch adhoc jobs
launcher-sessions-clusters is empty - all clusters may be used to launch session jobs
Cluster Kubernetes does not have any session images explicitly configured in /mnt/configmap/rstudio/rserver.conf or launcher-sessions-container-image config settings. Skipping launch of test job since we do not know which images we can use
/usr/sbin/rstudio-server: line 25: 1160 Segmentation fault /usr/lib/rstudio-server/bin/rserver --verify-installation=1 --server-daemonize=0 $1 $2 $3 $4 $5 $6 $7 $8
Checking Job Launcher configuration... Ensuring server-user is a Job Launcher admin... Getting list of Job Launcher clusters... Job launcher configured with the following clusters: Kubernetes launcher-adhoc-clusters is empty - all clusters may be used to launch adhoc jobs launcher-sessions-clusters is empty - all clusters may be used to launch session jobs Cluster Kubernetes does not have any session images explicitly configured in /mnt/configmap/rstudio/rserver.conf or launcher-sessions-container-image config settings. Skipping launch of test job since we do not know which images we can use
Exiting script because DIAGNOSTIC_ONLY=true
Setting launcher-sessions-container-image explicitly in rserver.conf allows it to run. However Jupyter and VS Code are skipped unless session-container-images is listed in jupyter.conf and vscode.conf
Setting
diagnostics.enabled: true
produces a segfault error in the pod logs:Setting
launcher-sessions-container-image
explicitly inrserver.conf
allows it to run. However Jupyter and VS Code are skipped unlesssession-container-images
is listed injupyter.conf
andvscode.conf