From 56ce095a48ec1a2643b87fd2bb17bd2d42aca107 Mon Sep 17 00:00:00 2001 From: Christian Goll Date: Wed, 3 Jul 2024 16:36:54 +0200 Subject: [PATCH] added cmd-line oci vars documentation Signed-off-by: Christian Goll --- userdocs/contents/containers.rst | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/userdocs/contents/containers.rst b/userdocs/contents/containers.rst index 2b89205d..6911a3a2 100644 --- a/userdocs/contents/containers.rst +++ b/userdocs/contents/containers.rst @@ -91,18 +91,15 @@ Here are the environmental variables that can be used. WAREWULF_OCI_PASSWORD WAREWULF_OCI_NOHTTPS -Here is an example: - +They can be overwritten with ``--nohttps``, ``--username`` and ``--passwd``. .. code-block:: console - # export WAREWULF_OCI_USERNAME=privateuser - # export WAREWULF_OCI_PASSWORD=super-secret-password-or-token - # wwctl import docker://ghcr.io/privatereg/rocky:8 + # wwctl import --username tux --passwd supersecret docker://ghcr.io/privatereg/rocky:8 The above is just an example. Consideration should be done before doing it this way if you are in a security sensitive environment or -shared environments. You would not want these showing up in bash -history or logs. +shared environments as this command line wil show up in the process +table. Local Files -----------