Greetings. We implemented RStudio app for RHEL7 using the ‘rserver-launcher-centos-7.simg’, pulled from shub://OSC/centos7-launcher.
We are now building the RStudio app for RHEL8 environment, and I’d like to implement what we did previously. Would someone be able to share an rstudio-server launcher image for CentOS8/RHEL8?
Thanks for checking in. This is built on RHEL8, and is the EasyBuild module RStudio-Server/1.4.1717-foss-2021a-Java-11-R-4.1.0
Here’s the full error, same whether launching via ‘rserver’ or ‘rstudio-server’:
$ rserver
23 Feb 2022 17:54:53 [rserver] ERROR system error 13 (Permission denied) [path: /var/run/rstudio-server, target-dir: ]; OCCURRED AT rstudio::core::Error rstudio::core::FilePath::createDirectory(const string&) const src/cpp/shared_core/FilePath.cpp:812; LOGGED FROM: int main(int, char* const*) src/cpp/server/ServerMain.cpp:602
These are good questions, Gerald. I’m not knowledgeable about RStudio and how it operates. In our RHEL7 cluster, where we use the launcher image, both the rserver and r processes run as unprivileged users. Running the rserver from the module fails as well:
$ rserver
23 Feb 2022 19:07:13 [rserver] WARNING Running as root user is not recommended!; LOGGED FROM: virtual rstudio::core::ProgramStatus rstudio::server::Options::read(int, char* const*, std::ostream&) src/cpp/server/ServerOptions.cpp:275
Next on my list is to discover where rstudio logs operational output.
I’ve installed r and rstudio-server on my ubuntu system, to hopefully educate myself further on how this software should operate. Thanks for your interest.
to reflect the altered file system supporting the new distribution (stream) model (I’m guessing a little on why the file system is different). Maybe it just reflects a different organization, RHEL7 vs 8.
Thanks, Gerald – The container will build from a root shell, but it’s not accessible via ‘singularity shell’ to check it’s contents. If I build via ‘sudo which singularity --sandbox <name.sif> <name.def>’, the build fails.
FATAL: While performing build: conveyor failed to get: while bootstrapping: exit status 1
Neglecting ‘–sandbox’, the build succeeds, with the failure upon testing:
hpc8 rstudio]$ singularity exec rstudio-launcher-centos-8.sif rserver
ERROR : No setuid installation found, for unprivileged installation use: ./mconfig --without-suid
Is there a way to verify the container, prior to attempt to implement it into the rstudio app workflow? The centos-7-launcher.sif shared through the ood docs allows to shell into it, so I’m assuming something has gone wrong in my container build.
Ahh…self-inflicted wounds. Turns out there is a problem with the singularity build on the RHEL8 cluster. Building from the definition file on the RHEL7 cluster generated an accessible container.
Will look to implement the app soon, using the centos-8-launcher.sif