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

What is the advantage of using init.R versus installing packages directly in Dockerfile with RUN Rscript -e install.packages...? #244

Open
joelostblom opened this issue Jan 26, 2021 · 2 comments

Comments

@joelostblom
Copy link

I would naively have done the latter, but the dash deployment docs are using init.R. Is this mostly to prevent the entire docker build from crashing if something is wrong with a user installed package or are there other advantages to this approach?

@joelostblom
Copy link
Author

Related, since the dash docks now uses install.packages('dash'), should the deployment docs be updated to use this instead of remotes::install_github('plotly/dashR', upgrade=TRUE)?

@joelostblom
Copy link
Author

One advantage I ran into is that when trying to install devtools via the docker image, the build would fail due to an error with the dependency packages gert and usethis. I had to modify apt-packages to include libgit2-dev and libcurl4-gnutls-dev instead of libcurl4-openssl-dev for these packages to install correctly and I am not sure if that has any side effects. When installing devtools via init.R everything works fine with the default apt-packages.

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

No branches or pull requests

1 participant