Skip to content

Add --vanilla to R call #1432

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

Merged
merged 2 commits into from
Aug 14, 2025
Merged

Add --vanilla to R call #1432

merged 2 commits into from
Aug 14, 2025

Conversation

rgaiacs
Copy link
Contributor

@rgaiacs rgaiacs commented Jul 9, 2025

Closes #1431

Edit: Copied description from #1431


Breaking changes

When R starts a new session as in

R

a couple of files from the current directory are executed, for example .Rprofile and .RData.

For the installation of R packages using install.R, a new R session is used. This means that .Rprofile and .RData and executed during the creation of the container image when install.R is executed.

This pull request will remove disable the execution of .Rprofile during the creation of the container image.

Users that are using .Rprofile to configure things during the creation of the image will observer that their intended changes are no longer present at the container image and the container image might be broken depending of their intended changes.

The .Rprofile is still executed when starting a new R session on Jupyter Notebooks, Jupyter Lab or R Studio.

Example

A user operates their own private mirror of CRAN at https:/cran.private.me and the .Rprofile has

options(repos=c(CRAN="https:/cran.private.me"))

With this pull request, when the user runs

repo2docker ...

the execution of install.R during the creation of the container image will use the official CRAN instead of the private mirror of the user.

@rgaiacs rgaiacs self-assigned this Jul 9, 2025
@rgaiacs rgaiacs requested a review from consideRatio August 1, 2025 13:10
@rgaiacs
Copy link
Contributor Author

rgaiacs commented Aug 14, 2025

A release of repo2docker was made in earlier August 2025. I propose that we merge this now so that we can expand a little the number of users for us to be able to re-assess this new feature. We can revert before the next release if we receive too many reports against it. What others thing?

Copy link
Member

@manics manics left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's been a month and no-one's raised any concrete objection on #1431

@manics manics merged commit 3899104 into jupyterhub:main Aug 14, 2025
21 checks passed
@consideRatio
Copy link
Member

Wieee I'm so glad about your very helpful attention around Jupyter @manics! Thank you @rgaiacs for all your contributions - you are getting a lot done!!! I'm especially glad about your work to fix intermittent CI failures - it makes a project go slower when everyone have to look into what a failure is about.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use --vanilla when running install.R
3 participants