From e0ef78b26ee2633b5ecacddf8a207a52b39b66cc Mon Sep 17 00:00:00 2001 From: Harmen Stoppels Date: Mon, 27 Nov 2023 17:36:00 +0100 Subject: docs: refer to oci build cache from containers.rst (#41269) --- lib/spack/docs/binary_caches.rst | 1 + lib/spack/docs/containers.rst | 10 ++++++++++ 2 files changed, 11 insertions(+) (limited to 'lib') diff --git a/lib/spack/docs/binary_caches.rst b/lib/spack/docs/binary_caches.rst index eeb6c4b783..dcc09910c7 100644 --- a/lib/spack/docs/binary_caches.rst +++ b/lib/spack/docs/binary_caches.rst @@ -182,6 +182,7 @@ section of the configuration: padded_length: 128 +.. _binary_caches_oci: ----------------------------------------- OCI / Docker V2 registries as build cache diff --git a/lib/spack/docs/containers.rst b/lib/spack/docs/containers.rst index 64ca1df926..acf48e3eae 100644 --- a/lib/spack/docs/containers.rst +++ b/lib/spack/docs/containers.rst @@ -24,6 +24,16 @@ image, or to set up a proper entrypoint to run the image. These tasks are usually both necessary and repetitive, so Spack comes with a command to generate recipes for container images starting from a ``spack.yaml``. +.. seealso:: + + This page is a reference for generating recipes to build container images. + It means that your environment is built from scratch inside the container + runtime. + + Since v0.21, Spack can also create container images from existing package installations + on your host system. See :ref:`binary_caches_oci` for more information on + that topic. + -------------------- A Quick Introduction -------------------- -- cgit v1.2.3-70-g09d2