-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rserver executable not found #538
Comments
Sorry for causing this. I think we can avoid this by specifying absolute paths as like |
When connecting to the session, i.e. opening |
@frederikziebell Yes, this is because $ find /usr/lib/rstudio-server/bin -maxdepth 1 -perm -111 -type f
/usr/lib/rstudio-server/bin/crashpad_handler
/usr/lib/rstudio-server/bin/rserver-pam
/usr/lib/rstudio-server/bin/pam-helper
/usr/lib/rstudio-server/bin/crash-handler-proxy
/usr/lib/rstudio-server/bin/rpostback
/usr/lib/rstudio-server/bin/crashpad_http_upload
/usr/lib/rstudio-server/bin/rsession
/usr/lib/rstudio-server/bin/r-ldpath
/usr/lib/rstudio-server/bin/rserver
/usr/lib/rstudio-server/bin/rstudio-server I made the change without knowing that singularity users use these....... |
Thanks, so I guess the fix is to just update https://github.com/rocker-org/rocker-versioned2/tree/master/scripts/rsession.sh |
@frederikziebell Are you using this file? |
I don't know. I just saw that my error was related to |
Is there any reason we can't just revert #535 and add |
The file
I do not want to add it to the PATH again for several reasons.
|
That seems reasonable to me. What about symlinking rserver, and maybe 1 or
2 other relevant executables into a directory on the default search path?
…On Tue, Sep 13, 2022, 9:41 AM eitsupi ***@***.***> wrote:
I don't know. I just saw that my error was related to rsession.sh and
assumed it would be copied to /etc/rstudio/ when the image is created. Do
you know how the R session is initiated after logging in to localhost:8787
?
The file rsession.sh does not exist in rocker/rstudio.
If you are using singularity with the procedure described on the following
page, it seems to be defined in the following line
https://github.com/rocker-org/website/blob/cddd1b2f333018739712b3143c46beb3e4f7bc9d/use/singularity.md?plain=1#L90-L95
Is there any reason we can't just revert #535
<#535> and add
/usr/lib/rstudio-server/bin/ to PATH again?
I do not want to add it to the PATH again for several reasons.
1. Since this repository divides functionality on a per-script basis,
it should rely as little as possible on the PATH environment variable,
which is impossible to set just by executing scripts.
https://github.com/rocker-org/rocker-versioned2/blob/37b57ec4c419967ce7e78105464b1b1a054cfac1/README.md?plain=1#L100-L106
2. RStudio Server works fine without setting PATH.
3. To reduce the effort of definition file maintenance.
—
Reply to this email directly, view it on GitHub
<#538 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZ2Z2BSMNLHITCEIVHEURDV6CAABANCNFSM6AAAAAAQKIRZGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
That's definitely a good idea, but I don't know which executables would be useful to have on the PATH (I don't use any of them). @cboettig Any thoughts? |
@eitsupi Then it seems symlinking |
I am wondering if |
Yes that makes sense, thanks! |
Personally, I would only use the rserver link, but I've migrated my recipes to use the absolute path. Maybe start with just rserver unless someone does a feature request? |
Ok, I am still a bit dubious about |
Container image name
rocker/rstudio:4.2.1
Container image digest
No response
What operating system are you seeing the problem on?
Linux
System information
Bug description
Running the rserver command inside a singulartiy container gives a
FATAL: "rserver": executable file not found in $PATH
error.How to reproduce this bug?
singularity pull docker://rocker/rstudio:4.2 singularity exec rstudio_4.2.sif rserver
Note: The issue does not occurr in
rocker/rstudio:4.1
.The text was updated successfully, but these errors were encountered: