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

manytestsr bootstrapping issue in bowers-prod-env.def #8

Open
mvanmoer opened this issue Apr 30, 2024 · 0 comments
Open

manytestsr bootstrapping issue in bowers-prod-env.def #8

mvanmoer opened this issue Apr 30, 2024 · 0 comments

Comments

@mvanmoer
Copy link
Contributor

mvanmoer commented Apr 30, 2024

Note to self -- I've been running into an issue where I:

  • install R through apt
  • install mamba and create a mamba R virtual env based on the exported conda list of packages. This virtual env is initialized and captured into a global shell script for use in %runscript when launching the container with $ singularity run <container>
  • manytestsr is installed through remotes::install_github(). remotes is installed during the creation of the mamba env, but is not visible to the R installed through apt. (Because the mamba env is not actually active in %post).

I tried redundantly installing remotes with an R one-liner and then installing manytestsr - and that is what minimal.def does, so I may build off of this to get the rest of the container set up.

I also tried to install R through mamba, creating the mamba env, and then activating the env while in %post but wasn't able to get that to work. That was partly because manytestsr is not seeing that every dependency is already installed in the mamba env and so pulls down all the sources and container build time almost quadrupled.

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