From f0e6f4bfccf667b58512fc63a53c2af6714d0cc6 Mon Sep 17 00:00:00 2001 From: jason yang Date: Tue, 12 Mar 2024 09:56:15 +0900 Subject: [PATCH] patch cherry picked docs Signed-off-by: jason yang --- build_env.rst | 3 +-- definition_files.rst | 3 +-- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/build_env.rst b/build_env.rst index 0ffbc3bf..561c9631 100644 --- a/build_env.rst +++ b/build_env.rst @@ -264,8 +264,7 @@ Environment Variables You can set environment variables on the host to influence the behaviour of a build. Note that environment variables are not passed into the build itself, and cannot be accessed in the ``%post`` section of a definition file. To pass values -into a build, use the :ref:`templating / build-args support ` -introduced in {Singularity} 4.0. +into a build, use the :ref:`templating / build-args support `. Environment variables that control a build are generally associated with an equivalent CLI option. The order of precendence is: diff --git a/definition_files.rst b/definition_files.rst index f545f906..4e92d36f 100755 --- a/definition_files.rst +++ b/definition_files.rst @@ -368,8 +368,7 @@ write configuration files, create new directories, etc. The commands in the ``%post`` section run in a clean environment. Environment variables from the host are not passed into the build. To pass values into a -build you should use the :ref:`templating / build-args support ` -introduced in {Singularity} 4.0. +build you should use the :ref:`templating / build-args support `. Consider the ``%post`` section from the example definition file above: