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

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

Open
yarikoptic opened this issue Apr 24, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@yarikoptic
Copy link
Member

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant