containerit
containerit copied to clipboard
o2r-project
Package an R workspace and all dependencies as a Docker container
Docker Hub API and sysreqs API are repeatedly called from the package. The user experience might be better if we cache the responses, e.g. using https://cran.r-project.org/web/packages/httpcache/
Extending #27 Relevant to all dialogs: - checkbox for versions - maintainer text field - image - Change the "Done" text to "Create" or something else - ... New features:...
Some `.Rmd` files for papers do not include code themselves, but link to script files via the `source("./script.R")` function. In these script files, there likely will be libraries required, as...
The best option is `sysreqs`. If that does not work I see this option: Ask users to create a PR based on a template for bespoke installation functions ``` containerit::bespoke_instructions
Show how you can use `containerit` and `stevedore` and _build arguments_ to put useful information into labels, e.g. build timestampe, build user, current git commit. Also show how to access...
See https://pak.r-lib.org/ _What are advantages for reproducibility?_
See https://www.jumpingrivers.com/blog/what-r-version-do-you-really-need-for-a-package/
Create a demo script that accepts environment variables as parameters and show how these can be changed when running the script within the container.
When packaging research into higher level containers, e.g. [ERC](http://dx.doi.org/10.1045/january2017-nuest), we most probably need some meta information. While the use can be asked for this, see #13, it would be better...
Potentially useful functions: - Using `pkggraph` we could explicitly list all R package dependencies of the loaded packages in the Dockerfile. See https://cran.r-project.org/web/packages/pkggraph/vignettes/vignette_pkggraph.html - `tools` package could also already do...
Metadata
Owner
Metadata
Package an R workspace and all dependencies as a Docker container