containers
/
automation-tests
mirror of https://github.com/containers/automation-tests.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify the documentation of containers.env 

* Document that variables can be listed without a value. Experimentally,
  this worked for me, and it's documented in podman's `--env`. I'm
  guessing supporting this in containers.conf too was intentional?
* Document that this config setting is ignored by `podman exec`, see
  https://github.com/containers/podman/issues/25685

Fixes: https://github.com/containers/podman/issues/25685
Signed-off-by: David Mandelberg <david@mandelberg.org>
This commit is contained in:
David Mandelberg 2025-03-26 14:21:49 -04:00
parent d093d6c769
commit 4af2f86f37
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
common/docs/containers.conf.5.md
View File

@ -199,7 +199,12 @@ container. The special value “none” can be specified to disable creation of
**env**=["PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"]
Environment variable list for the container process, used for passing
environment variables to the container.
environment variables to the container. If a variable is listed without a value,
the value is copied from the host environment.
Note that this is only used when a container is created, not with subsequent
commands like `podman exec`. This prevents variables in the config file from
overwriting values specified on the command line when the container was created.
**env_host**=false