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

Make 2021.06 available as container image and/or tarball #102

Open
bedroge opened this issue Nov 22, 2021 · 0 comments
Open

Make 2021.06 available as container image and/or tarball #102

bedroge opened this issue Nov 22, 2021 · 0 comments

Comments

@bedroge
Copy link
Collaborator

bedroge commented Nov 22, 2021

When 2021.12 is available, we should not just delete 2021.06, but use it for testing a still to be developed script that can export that version to tarballs / container images.

The resulting tarballs can be stored in, for instance, a S3 bucket. The container images could go into the GHCR and/or another registry (AWS, Docker Hub)

@ocaisa came up with a nice suggestion to replace the directory of such a version by a variant symlink, which allows users to extract the tarball to some location and configure the variant symlink (in their local CVMFS config) to point to that location. This will allow them to keep using a version that's no longer available on CVMFS.

@bedroge bedroge moved this to Todo filesystem layer in EESSI pilot 2021.12 Nov 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo filesystem layer
Development

No branches or pull requests

1 participant