diff options
| author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2021-10-25 22:09:27 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-10-25 13:09:27 -0700 |
| commit | 6063600a7bff427d5ae404cd8386186026191228 (patch) | |
| tree | f5b8830e38dea74546fffcc9e46d21fad7a6cbc1 /LICENSE-APACHE | |
| parent | ff65e6352f1a3d906514fed971f074115b97ded2 (diff) | |
| download | spack-6063600a7bff427d5ae404cd8386186026191228.tar.gz spack-6063600a7bff427d5ae404cd8386186026191228.tar.bz2 spack-6063600a7bff427d5ae404cd8386186026191228.tar.xz spack-6063600a7bff427d5ae404cd8386186026191228.zip | |
containerize: pin the Spack version used in a container (#21910)
This PR permits to specify the `url` and `ref` of the Spack instance used in a container recipe simply by expanding the YAML schema as outlined in #20442:
```yaml
container:
images:
os: amazonlinux:2
spack:
ref: develop
resolve_sha: true
```
The `resolve_sha` option, if true, verifies the `ref` by cloning the Spack repository in a temporary directory and transforming any tag or branch name to a commit sha. When this new ability is leveraged an additional "bootstrap" stage is added, which builds an image with Spack setup and ready to install software. The Spack repository to be used can be customized with the `url` keyword under `spack`.
Modifications:
- [x] Permit to pin the version of Spack, either by branch or tag or sha
- [x] Added a few new OSes (centos:8, amazonlinux:2, ubuntu:20.04, alpine:3, cuda:11.2.1)
- [x] Permit to print the bootstrap image as a standalone
- [x] Add documentation on the new part of the schema
- [x] Add unit tests for different use cases
Diffstat (limited to 'LICENSE-APACHE')
0 files changed, 0 insertions, 0 deletions