Skip to content

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

@mvanmoer

Description

@mvanmoer

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions