Skip to content

Manual push containers #3411

@bernt-matthias

Description

@bernt-matthias

Have some older versions of tools that need containers which can only be built with some additional requirements. I use this issue to keep track of and document transparently .. and someone may push them manually:

  • https://toolshed.g2.bx.psu.edu/repos/yguitton/metams_rungc/file/c75532b75ba1
    • DEST_BASE_IMAGE="quay.io/bioconda/base-glibc-busybox-bash:latest" bioconductor-metams=1.8.0,bioconductor-xcms=1.46.0,r-batch=1.1_4,r-base=3.4.1,libgfortran=3.0.0,libgfortran4=7.5.0 mulled-build build --verbose --name-override mulled-v2-8e43efd53951b49bbcd3d50a883c93ef9038a927:51a49b963d243ab8961ab7a9d9dd698d7c1c5386-0 --namespace biocontainers
    • I accidentally made this which created a container with a "wrong hash"
    • MetaMS will be added to W4M repo .. so there will be containers for future versions of the tool
  • https://toolshed.g2.bx.psu.edu/repos/lecorguille/msnbase_readmsdata/file/d7a7ef786fbe
    • DEST_BASE_IMAGE="quay.io/bioconda/base-glibc-busybox-bash:latest" mulled-build build bioconductor-msnbase=2.4.0,r-batch=1.1_4,unzip=6.0,libgfortran=3.0.0 --verbose --name-override mulled-v2-60009da30ffd85f87811b22d88de712b63dd80ae:a76e3a712b8e1271923ac8af141f707635749ba1-0 --namespace biocontainers
    • the container is for an old version of the tool, it is now part of W4M, i.e. containers are generated

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