diff options
author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2020-11-17 20:25:13 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-11-17 11:25:13 -0800 |
commit | 5f636fc3177a1ad5d5a2bc1a1471e6fa23106d99 (patch) | |
tree | 2291442db370659f098472e33e7d68d0536455df /.github | |
parent | 7ffad278d34bcc1bda7d5d355e1104a10a7c484a (diff) | |
download | spack-5f636fc3177a1ad5d5a2bc1a1471e6fa23106d99.tar.gz spack-5f636fc3177a1ad5d5a2bc1a1471e6fa23106d99.tar.bz2 spack-5f636fc3177a1ad5d5a2bc1a1471e6fa23106d99.tar.xz spack-5f636fc3177a1ad5d5a2bc1a1471e6fa23106d99.zip |
spack containerize: allow users to customize the base image (#15028)
This PR reworks a few attributes in the container subsection of
spack.yaml to permit the injection of custom base images when
generating containers with Spack. In more detail, users can still
specify the base operating system and Spack version they want to use:
spack:
container:
images:
os: ubuntu:18.04
spack: develop
in which case the generated recipe will use one of the Spack images
built on Docker Hub for the build stage and the base OS image in the
final stage. Alternatively, they can specify explicitly the two
base images:
spack:
container:
images:
build: spack/ubuntu-bionic:latest
final: ubuntu:18.04
and it will be up to them to ensure their consistency.
Additional changes:
* This commit adds documentation on the two approaches.
* Users can now specify OS packages to install (e.g. with apt or yum)
prior to the build (previously this was only available for the
finalized image).
* Handles to avoid an update of the available system packages have been
added to the configuration to facilitate the generation of recipes
permitting deterministic builds.
Diffstat (limited to '.github')
0 files changed, 0 insertions, 0 deletions