Skip to content

Support having multiple versions of containers, and specification of version upon execution #266

@yarikoptic

Description

@yarikoptic

Idea was formulated by @jbwexler in

  1. specification @jbwexler suggested there to have smth like
[datalad "containers.bids-fmriprep]
    cmdexec = {img_dspath}/scripts/singularity_cmd run {img} {cmd}
    image = images/bids/bids-fmriprep--{version}.sing
    default_version = 20.2.0

or even just

[datalad "containers.bids-fmriprep]
    cmdexec = {img_dspath}/scripts/singularity_cmd run {img} {cmd}
    image = images/bids/bids-fmriprep--{version}.sing
    version = 20.2.0

hence version specifying the default one but us allowing to overload it while naming which container to run:

  1. making it possible to specify version while running e.g. as -n {NAME}={version} or adding explicit --version to overload that version in the specification.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions