# RStudio version too old

**URL:** <https://renku.discourse.group/t/rstudio-version-too-old/393>\
**Category:** RenkuLab\
**Created:** [5 August 2021 09:49 UTC](https://renku.discourse.group/t/rstudio-version-too-old/393 "2021-08-05T09:49:11Z")\
**Posts on this page:** 12\
**Page:** 2

<div class="post-metadata">

**Author:** ![lgatto](https://yyz2.discourse-cdn.com/free1/user_avatar/renku.discourse.group/lgatto/32/64_2.png) [@lgatto](https://renku.discourse.group/u/lgatto)\
**Post date:** [16 September 2021 13:06 UTC](https://renku.discourse.group/t/rstudio-version-too-old/393/21 "2021-09-16T13:06:42Z")

</div>

Grrr - now it throws me an error 500 : Internal Server Error. I must have an error somewhere, but can’t spot it. I might be better off starting from your project.

---

<div class="post-metadata">

**Author:** ![tao.sun](https://yyz2.discourse-cdn.com/free1/user_avatar/renku.discourse.group/tao.sun/32/269_2.png) [@tao.sun](https://renku.discourse.group/u/tao.sun)\
**Post date:** [16 September 2021 13:30 UTC](https://renku.discourse.group/t/rstudio-version-too-old/393/22 "2021-09-16T13:30:35Z")

</div>

Hi @lgatto, i [forked](https://renkulab.io/projects/tao.sun/wsbim-bioinfo) your project and found that the error came from the last line in Dockerfile:

`RUN pip3 install jupyter-rsession-proxy==1.2.0 jupyter-server-proxy==1.5.0`

which actually undoes some fix I did.

For simplicity, I also commented the installation of R packages in my fork, which imo has nothing to do with this 500 error.

---

<div class="post-metadata">

**Author:** ![lgatto](https://yyz2.discourse-cdn.com/free1/user_avatar/renku.discourse.group/lgatto/32/64_2.png) [@lgatto](https://renku.discourse.group/u/lgatto)\
**Post date:** [16 September 2021 14:06 UTC](https://renku.discourse.group/t/rstudio-version-too-old/393/23 "2021-09-16T14:06:33Z")

</div>

Indeed, all is working now. Thank you again so much for your help!

---

<div class="post-metadata">

**Author:** ![kendavidn](https://yyz2.discourse-cdn.com/free1/user_avatar/renku.discourse.group/kendavidn/32/394_2.png) [@kendavidn](https://renku.discourse.group/u/kendavidn)\
**Post date:** [1 February 2022 09:45 UTC](https://renku.discourse.group/t/rstudio-version-too-old/393/24 "2022-02-01T09:45:44Z")

</div>

Hello!

I have successfully forked [this project](https://renkulab.io/projects/laurent.gatto/wsbim-bioinfo) and am able to open a session with RStudio 1.4 with it.

I am wondering how to copy this behavior to other projects? Which files should I copy?

Thank you very much

---

<div class="post-metadata">

**Author:** ![gavin-k-lee](https://yyz2.discourse-cdn.com/free1/user_avatar/renku.discourse.group/gavin-k-lee/32/233_2.png) [@gavin-k-lee](https://renku.discourse.group/u/gavin-k-lee)\
**Post date:** [1 February 2022 09:54 UTC](https://renku.discourse.group/t/rstudio-version-too-old/393/25 "2022-02-01T09:54:27Z")

</div>

Hi Kene,

Thank you for following up on this! We are currently working very hard to release a suite of R \>= 4.1.0 + RStudio \>= 1.4 Docker images and corresponding project templates - they should be ready soon and rolled out to the usual project creation pages shortly.

If you requirea quick fix immediately, the files you would need to look at in that project are the `Dockerfile` and `.renku/renku.ini`.

For the Dockerfile: Instead of `FROM renku/renkulab-r4.0.5...` that you may have in your existing R project, you could try the one in that project, which started with `FROM ableuler/wsbim-fix:2`.

For `.renku/renku.ini` file you should copy the one used in the project (the second line of it looks like this: `default_url = /rstudio/auth-sign-in?appUrl=%2Fworked`).

Let us know if that works or you need some extra help in your case!

Gavin

---

<div class="post-metadata">

**Author:** ![kendavidn](https://yyz2.discourse-cdn.com/free1/user_avatar/renku.discourse.group/kendavidn/32/394_2.png) [@kendavidn](https://renku.discourse.group/u/kendavidn)\
**Post date:** [3 February 2022 23:21 UTC](https://renku.discourse.group/t/rstudio-version-too-old/393/26 "2022-02-03T23:21:37Z")

</div>

Thank you very much Gavin.

I seem to still be having a bit of an issue with this. When I change the renku.ini file, starting a session leads me to an RStudio login page, which I am unable to get past.

 ![CleanShot 2022-02-04 at 00.20.23@2x](https://global.discourse-cdn.com/free1/uploads/renku/original/1X/202f484abebd3a369a63937e3f82c08dbf1fb5b5.jpeg)

Might I be doing something wrong?

([Here](https://renkulab.io/projects/thegraphcourses/introduction-to-data-analysis-with-r/files/blob/.renku/renku.ini) is the project I would like students to fork and be able to run with RStudio \>1.4)

---

<div class="post-metadata">

**Author:** ![gavin-k-lee](https://yyz2.discourse-cdn.com/free1/user_avatar/renku.discourse.group/gavin-k-lee/32/233_2.png) [@gavin-k-lee](https://renku.discourse.group/u/gavin-k-lee)\
**Post date:** [4 February 2022 00:02 UTC](https://renku.discourse.group/t/rstudio-version-too-old/393/27 "2022-02-04T00:02:58Z")

</div>

Hi Kene,

We have started to build some R/RStudio images that are recent, but they have not been released yet/fully tested. However, you can still try it. You will probably need to open the session in a new tab to make sure it works.

Steps:

1. Dockerfile: Use the following ‘from’ statement: `FROM renku/renkulab-r:4.1.0-846186f`
2. .renku/renku.ini: Remove the ‘hacky’ existing one and use this:

```auto
[renku "interactive"]
default_url = /rstudio

```

You will then need to let the image build and then you can try to open a session once it’s built. The RStudio version will be \>1.4 (they have renamed them to calendar versioning now), with R 4.1.0.

Thanks for your patience!! Let me know how it goes - we are still testing those images.

---

<div class="post-metadata">

**Author:** ![lgatto](https://yyz2.discourse-cdn.com/free1/user_avatar/renku.discourse.group/lgatto/32/64_2.png) [@lgatto](https://renku.discourse.group/u/lgatto)\
**Post date:** [4 February 2022 07:35 UTC](https://renku.discourse.group/t/rstudio-version-too-old/393/28 "2022-02-04T07:35:38Z")

</div>

Hello - thank you for updating the Renku R infrastructure. This is really important for us R/Renku users.

Just a little suggestion though - I see you target R 4.1.0. The latest version is 4.1.2; while it’s only a patched upgrade, it might we worth (and hopefully easy) to go the that one.

More generally, and to be able to get contributions from the community, where can I find the information to do the same for, say, R-devel? We aren’t too far from the release of R 4.2 (March - April, I think).

---

<div class="post-metadata">

**Author:** ![gavin-k-lee](https://yyz2.discourse-cdn.com/free1/user_avatar/renku.discourse.group/gavin-k-lee/32/233_2.png) [@gavin-k-lee](https://renku.discourse.group/u/gavin-k-lee)\
**Post date:** [4 February 2022 07:39 UTC](https://renku.discourse.group/t/rstudio-version-too-old/393/29 "2022-02-04T07:39:26Z")

</div>

Hi there - thanks for the suggestion! We are planning on expanding the suite to:

R: 4.1.0, 4.1.1, 4.1.2, devel; and  
Bioc: 3.13, 3.14, devel,

since R 4.0.5 came out in March 2021 and Bioc 3.12 in October 2020. Would that be sufficient at this point in time?

---

<div class="post-metadata">

**Author:** ![kendavidn](https://yyz2.discourse-cdn.com/free1/user_avatar/renku.discourse.group/kendavidn/32/394_2.png) [@kendavidn](https://renku.discourse.group/u/kendavidn)\
**Post date:** [4 February 2022 11:10 UTC](https://renku.discourse.group/t/rstudio-version-too-old/393/30 "2022-02-04T11:10:52Z")

</div>

Thank you very much! This seems to work for me!

---

<div class="post-metadata">

**Author:** ![lgatto](https://yyz2.discourse-cdn.com/free1/user_avatar/renku.discourse.group/lgatto/32/64_2.png) [@lgatto](https://renku.discourse.group/u/lgatto)\
**Post date:** [4 February 2022 13:51 UTC](https://renku.discourse.group/t/rstudio-version-too-old/393/31 "2022-02-04T13:51:33Z")

</div>

For now, these version are great, but the next version of R, and thus Bioconductor will be released in March, and quickly become desirable. These would, for example, become critical for all courses starting thereafter (for instance in Sept 2022).

The situation is a but confusing because R has a yearly release schedule (in March/April) and Bioconductor is released every 6 month and Bioconductor versions match specific R version. Currently Bioc 3.14 (stable release) requires R 4.1.1 (or 4.1.2) and Bioc 3.15 (devel) requires R-devel. Once R 4.2 is released, Bioc 3.15 will be released as stable version and a new Bioc devel branch will be started. (See also [here](http://contributions.bioconductor.org/use-devel.html) for more details on the R and Bioc version dependencies.)

This essentially means that it is not unlikely that a new R/Bioc Renku environment would be needed. The [Bioconductor docker containers](http://bioconductor.org/help/docker/) could be helpful here.

---

<div class="post-metadata">

**Author:** ![rrrrrok](https://yyz2.discourse-cdn.com/free1/user_avatar/renku.discourse.group/rrrrrok/32/117_2.png) [@rrrrrok](https://renku.discourse.group/u/rrrrrok)\
**Post date:** [4 February 2022 14:38 UTC](https://renku.discourse.group/t/rstudio-version-too-old/393/32 "2022-02-04T14:38:22Z")

</div>

Hi @lgatto, we should be OK to easily add new R versions in the future. The underlying incompatibility between Jupyter and RStudio seems to have been resolved, which is why we are finally unblocked on this (thanks to @tolevski and @gavin-k-lee). As far as the bioc images go, we are already using the bioconductor docker images as the base for those builds, see [here](https://github.com/SwissDataScienceCenter/renkulab-docker/blob/e3379bf2202473a4d0ce51ac1e84f6acc2177585/.github/workflows/build_and_push_to_docker.yml#L436).

[Previous page](https://renku.discourse.group/t/rstudio-version-too-old/393.md?page=1)
