Apptainer / Singularity insufficient build encapsulation #50
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
inm7/inm-icf-utilities#50
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I can build the container image with
apptainer(everything applies forsingularity, too):When, for some reason, I want to build the image again, it fails:
The runs leave behind, in the host system's
/tmpthese files, produced bydatalad-installer:Removing the
/tmp/dlinstaller_env.shfile allows the new build to proceed:Crucially, the same would hapen if, e.g.
/tmp/dlinstaller_env.shwas already present for unrelated reasons (e,g. created by datalad-installer).This is probably not very alarming (given that
/tmpis usually wiped on reboot) but maybe we can improve on build encapsulation.Note:
datalad-installerappends to the/tmp/dlinstaller_env.shfile; thecutcommand used in the definition file to get the temporary directory produces two lines of output if the file has two lines.Reported by Stefanie
this should work:
but I am also tempting to do what datalad-installer does:
(plus, probably, setting the env variable explicitly)