docs: refer to oci build cache from containers.rst (#41269)
This commit is contained in:
parent
d768e6ea5c
commit
e0ef78b26e
2 changed files with 11 additions and 0 deletions
|
@ -182,6 +182,7 @@ section of the configuration:
|
||||||
padded_length: 128
|
padded_length: 128
|
||||||
|
|
||||||
|
|
||||||
|
.. _binary_caches_oci:
|
||||||
|
|
||||||
-----------------------------------------
|
-----------------------------------------
|
||||||
OCI / Docker V2 registries as build cache
|
OCI / Docker V2 registries as build cache
|
||||||
|
|
|
@ -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
|
usually both necessary and repetitive, so Spack comes with a command
|
||||||
to generate recipes for container images starting from a ``spack.yaml``.
|
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
|
A Quick Introduction
|
||||||
--------------------
|
--------------------
|
||||||
|
|
Loading…
Reference in a new issue