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

Specifying more extra_inputs like overlays #189

Closed
nobodyinperson opened this issue Jan 19, 2023 · 1 comment · Fixed by #190
Closed

Specifying more extra_inputs like overlays #189

nobodyinperson opened this issue Jan 19, 2023 · 1 comment · Fixed by #190

Comments

@nobodyinperson
Copy link
Contributor

Asked in chat:

Is there an more elegant way of specifying an additional --overlay image with datalad containers-add than hard-coding it in --call-fmt and specifying the overlay image as --input in each datalad containers-run?

A little less hard-coding can be achieved by putting the overlay next to the Apptainer/Singularity image and naming it exactly the same just with a suffix (e.g. -overlay.img), then use --call-fmt 'apptainer exec --overlay {img}-overlay.img {img} {cmd}'. Still need to specify the overlay as --input in containers-run though...

It would be helpful if one could do:

datalad containers-add NAME \
   --extra-input containers/overlay.img \
   --call-fmt 'apptainer exec --overlay {imgdir}/overlay.sif {img} {cmd}' \
   -i containers/container.sif
@github-actions
Copy link

Issue fixed in 1.2.0

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

Successfully merging a pull request may close this issue.

1 participant