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

[BUG] renv::restore() fails under v1.0.3 but is successful using v0.17.3 #1741

Closed
campbead opened this issue Oct 26, 2023 · 3 comments
Closed
Labels
bug an unexpected problem or unintended behavior install 🧺
Milestone

Comments

@campbead
Copy link

I am running renv::restore() as part of the following docker_build command:

docker build -f Dockerfile_base --progress=plain -t golem.test.project_base .

where Dockerfile_base is:

FROM rocker/verse:4.2.2
RUN mkdir -p /usr/local/lib/R/etc/ /usr/lib/R/etc/
RUN echo "options(renv.config.pak.enabled = TRUE, repos = c(CRAN = 'https://cran.rstudio.com/'), download.file.method = 'libcurl', Ncpus = 4)" | tee /usr/local/lib/R/etc/Rprofile.site | tee /usr/lib/R/etc/Rprofile.site
RUN R -e 'install.packages(c("renv","remotes"))'
COPY renv.lock renv.lock
RUN R -e 'renv::restore()'

this results in the following error:

278238375-e91d6bc8-d5e0-403f-b634-39e212c01812

I have attempted fix by changing Dockerfile_base to force an install of renv version 0.17.3 to:

FROM rocker/verse:4.2.2
RUN mkdir -p /usr/local/lib/R/etc/ /usr/lib/R/etc/
RUN echo "options(renv.config.pak.enabled = TRUE, repos = c(CRAN = 'https://cran.rstudio.com/'), download.file.method = 'libcurl', Ncpus = 4)" | tee /usr/local/lib/R/etc/Rprofile.site | tee /usr/lib/R/etc/Rprofile.site
RUN R -e 'install.packages("remotes")'
RUN R -e 'remotes::install_version("renv", version = "0.17.3")'
COPY renv.lock renv.lock
RUN R -e 'renv::restore()'

which results in a successful build when using the docker build command.

I believe this might relate to this bug and is affecting golem package upstream.

I have attached my renv.lock file as renv.lock.txt so that i can upload it here.

Thank you for any help. Please let me know if any addition information is needed.

@kevinushey
Copy link
Collaborator

Thanks for the bug report, and sorry for the delay. It seems like this issue may be resolved with pak 0.7.0; I'm no longer able to reproduce. Are you still seeing this issue?

@campbead
Copy link
Author

campbead commented Dec 14, 2023

I can confirm that I no longer see the issue. I will close the ticket now. Thank you

-Adam

@kevinushey
Copy link
Collaborator

Awesome news; thanks for confirming!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug an unexpected problem or unintended behavior install 🧺
Projects
None yet
Development

No branches or pull requests

2 participants