Support '--env-file flag with OCI launcher. #1030
Labels
Milestone
Comments
17 tasks
dtrudg
added
enhancement
dtrudg
added a commit
to dtrudg/singularity
that referenced
this issue
Dec 6, 2022
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs#1030
dtrudg
added a commit
to dtrudg/singularity
that referenced
this issue
Dec 7, 2022
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs#1030
edytuk
pushed a commit
to vzokay/apptainer
that referenced
this issue
Jan 26, 2023
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs/singularity#1030 Signed-off-by: Edita Kizinevic <edita.kizinevic@cern.ch>
edytuk
pushed a commit
to vzokay/apptainer
that referenced
this issue
Feb 9, 2023
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs/singularity#1030 Signed-off-by: Edita Kizinevic <edita.kizinevic@cern.ch>
edytuk
pushed a commit
to vzokay/apptainer
that referenced
this issue
Feb 11, 2023
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs/singularity#1030 Signed-off-by: Edita Kizinevic <edita.kizinevic@cern.ch>
edytuk
pushed a commit
to vzokay/apptainer
that referenced
this issue
Feb 11, 2023
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs/singularity#1030 Signed-off-by: Edita Kizinevic <edita.kizinevic@cern.ch>
edytuk
pushed a commit
to vzokay/apptainer
that referenced
this issue
Feb 23, 2023
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs/singularity#1030 Signed-off-by: Edita Kizinevic <edita.kizinevic@cern.ch>
edytuk
pushed a commit
to vzokay/apptainer
that referenced
this issue
Mar 31, 2023
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs/singularity#1030 Signed-off-by: Edita Kizinevic <edita.kizinevic@cern.ch>
edytuk
pushed a commit
to vzokay/apptainer
that referenced
this issue
May 24, 2023
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs/singularity#1030 Signed-off-by: Edita Kizinevic <edita.kizinevic@cern.ch>
edytuk
pushed a commit
to vzokay/apptainer
that referenced
this issue
May 24, 2023
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs/singularity#1030 Signed-off-by: Edita Kizinevic <edita.kizinevic@cern.ch>
edytuk
pushed a commit
to vzokay/apptainer
that referenced
this issue
Jun 14, 2023
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs/singularity#1030 Signed-off-by: Edita Kizinevic <edita.kizinevic@cern.ch>
edytuk
pushed a commit
to vzokay/apptainer
that referenced
this issue
Jun 14, 2023
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs/singularity#1030 Signed-off-by: Edita Kizinevic <edita.kizinevic@cern.ch>
edytuk
pushed a commit
to vzokay/apptainer
that referenced
this issue
Jun 16, 2023
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs/singularity#1030 Signed-off-by: Edita Kizinevic <edita.kizinevic@cern.ch>
edytuk
pushed a commit
to vzokay/apptainer
that referenced
this issue
Jul 4, 2023
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs/singularity#1030 Signed-off-by: Edita Kizinevic <edita.kizinevic@cern.ch>
edytuk
pushed a commit
to vzokay/apptainer
that referenced
this issue
Jul 11, 2023
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs/singularity#1030 Signed-off-by: Edita Kizinevic <edita.kizinevic@cern.ch>
edytuk
pushed a commit
to vzokay/apptainer
that referenced
this issue
Jul 21, 2023
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs/singularity#1030 Signed-off-by: Edita Kizinevic <edita.kizinevic@cern.ch>
edytuk
pushed a commit
to vzokay/apptainer
that referenced
this issue
Jul 24, 2023
Allow --env-file to be used to provide environment variables in a file, when running a container in --oci mode. We use the same approach as the native runtime for compatibility. The env file is evaluated in the embedded shell interpreter, but starting with an empty environment. This handles quoting, comments etc. for us, and keeps maximum compatibility with the existing handling. Fixes sylabs/singularity#1030 Signed-off-by: Edita Kizinevic <edita.kizinevic@cern.ch>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Set environment variable values from a file provided via the CLI --env-file option in the config.json for the container launched via the OCI launcher.
Note any differences with variable interpretation, versus the singularity runtime, and add warning messages where an env var might be subject to these differences.
The text was updated successfully, but these errors were encountered: