-
Notifications
You must be signed in to change notification settings - Fork 2
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
rudimentary SIF image cache for apptainer/singularity runners #141
Comments
I'm still thinking about if this is a good idea. The main reason I chose to avoid this when first writing
These questions still leave me unconvinced that have a shared cache is a good idea. Especially this last point which goes almost completely against the whole idea of Currently,
Edit: I've confirmed via |
Is your feature request related to a problem? Please describe.
I don't like how many copies of a SIF image I need to have. For example, if I have two projects that both want to use the
python:3.12
image for the denv, they both need to have their own copy of it within.denv/images
.Describe the solution you'd like
I think we can piggy-back on
APPTAINER_CACHEDIR
and keep the denv images within some subdirectory there so images can be shared between multiple denvs held by a single user. The downside then is that if one denv chooses to update an image (withdenv config image pull
) this could effect other denvs using the same image.Describe alternatives you've considered
Users can still avoid image duplicated by using symlinks. They could create their own location of SIF files and then pass the full path to the SIF file to
denv
when initializing or configuring. I don't like this solution because it requires the user toapptainer build
themselves which is less ergonomic than lettingdenv
get the OCI image they want into the correct format.Additional context
If implemented, this will also hopefully improve the speed of the apptainer/singularity tests since the OCI-SIF image conversion will only need to happen once per image name rather than for every test.
The text was updated successfully, but these errors were encountered: