Skip to content
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

RStudio fails to start because jammy-build is installed in buildpack-deps:bionic #1290

Closed
yamaton opened this issue Jun 30, 2023 · 1 comment · Fixed by #1293
Closed

RStudio fails to start because jammy-build is installed in buildpack-deps:bionic #1290

yamaton opened this issue Jun 30, 2023 · 1 comment · Fixed by #1293

Comments

@yamaton
Copy link
Contributor

yamaton commented Jun 30, 2023

Bug description

  • OS: Linux
  • repo2docker version: 2023.06.0

RStudio fails to start due to missing libssl.so.3 when installed with r-base=4.2 in environment.yml. The issue occurs because rstudio-server for jammy is somehow installed on buildpack:bionic.

Note: This issue might be temporary due to the ongoing transition: #1287

How to reproduce

This environment.yml is what I'm testing with. It's from binder-examples/r-conda, but changed r-base to 4.2.

channels:
  - conda-forge
dependencies:
  - r-base=4.2
  - r-tidyverse

Then RStudio fails to start with the error:

/usr/lib/rstudio-server/bin/rserver: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory

From the Terminal within the container, we see the system is bionic while rstudio-server is for jammy.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.6 LTS
Release:        18.04
Codename:       bionic

$ rstudio-server version
2022.12.0+353 (Elsbeth Geranium) for Ubuntu Jammy

Binder links

I suppose mybinder.org now uses repo2docker 2023.06.0. So the issue is reproduced there.

Jupyter+R: Binder

RStudio: Binder

[EDIT] When called with the command-line option --Repo2Docker.base_image=docker.io/library/buildpack-deps:jammy, RStudio starts fine.

[EDIT2] apt-cache search libssl3 returns the exit code 0 even when there is no hit. So this line would be erroneous.

[EDIT3] My suggestion is to replace it with ldconfig -p | grep -q libssl3.

[EDIT4] Settled to apt-cache search libssl3 | grep -q libssl3 and created a PR.

@welcome
Copy link

welcome bot commented Jun 30, 2023

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
welcome
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

@yamaton yamaton changed the title RStudio fails to start because jammy version is installed on buildpack:bionic RStudio fails to start because jammy-build is installed in buildpack-deps:bionic Jul 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant