Skip to content

Commit 65236ea

Browse files
gwangmubcumming
andauthored
Update docs/software/container-engine/known-issue.md
Co-authored-by: Ben Cumming <[email protected]>
1 parent 597ac6f commit 65236ea

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

docs/software/container-engine/known-issue.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,8 @@ Defining a mount related to `/users` in the EDF should only be done when there i
5656
[](){#ref-ce-why-no-sbatch-env}
5757
## Why `--environment` as `#SBATCH` is discouraged
5858

59-
Due to how Slurm works, when using `--environment` as an `#SBATCH` option, the entire content of the SBATCH script is executed within a container created by the EDF file. This may cause several counterintuitive implications that can lead to subtle and hard-to-diagnose failures. The following are a few known issues associated with `--environment` in SBATCH.
59+
Due to how Slurm works, when using `--environment` as an `#SBATCH` option, the entire contents of the SBATCH script is executed within a container created by the EDF file.
60+
This can lead to subtle and hard-to-diagnose failures, some of which are described below.
6061

6162
- **Slurm availability in the container**: In some cases, CE does not inject essential Slurm components in containers, which result in crashes on basic Slurm operations (e.g., `srun`) inside the SBATCH script. Even if they were injected, it's not guaranteed to cover the complete feature set of Slurm.
6263

0 commit comments

Comments
 (0)