-
Notifications
You must be signed in to change notification settings - Fork 17
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
provide good docker image for pkg devel #106
Comments
naturally, this wouldn't apply for some of the "later" actions, such as |
I am not sure the RStudio ones actually exist currently, so I think relying on the R-hub ones seems like the best plan in the short term. |
ubuntu-gcc-release it is. |
talked with **** (RStudio employee) yesterday and s/he suggested to take a look at
Mariana-trench deep backlog, my favorite place for issues. |
The repo is here FWIW https://github.com/rstudio/r-docker, they are versioned by OS and R version, so you can use rstudio/r-base:3.5-xenial for R 3.5 on xenial etc. |
currently, ghactions (and all R actions contained therein) require that the user bring her own docker image, such as
rocker/tidyverse
, or whatever really.This makes some sense for random rmd projects (etc.), where the compute environment might well be arbitrary.
It makes a lot less sense for CRAN-bound pkg-dev, where we're usually targeting a pretty well-defined compute environment (CRAN checks)
So it might make sense to default to / standardise on one docker image to run some of the pkg dev actions in. (And this is what the current focus of the project is).
The question is which image (in order of my descending, gut-feeling preference):
rocker/r-ver
.@jimhester so my suggestion would be:
This would imply:
The text was updated successfully, but these errors were encountered: