You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/software/container-engine.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -389,6 +389,19 @@ It is possible to use environment variables to control which capabilities of the
389
389
Additionally, the NVIDIA Container Toolkit can enforce specific constraints for the container, for example, on versions of the CUDA runtime or driver, or on the architecture of the GPUs.
390
390
For the full details about using these features, please refer to the official documentation: [Driver Capabilities](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/docker-specialized.html#driver-capabilities), [Constraints](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/docker-specialized.html#constraints).
391
391
392
+
[](){#ref-ce-container-hooks}
393
+
## Container Hooks
394
+
395
+
Container hooks let you customize container behavior to fit system-specific needs, making them especially valuable for High-Performance Computing.
396
+
397
+
**What they do*: Hooks extend container runtime functionality by enabling custom actions during a container's lifecycle.
398
+
**Use for HPC*: HPC systems rely on specialized hardware and fine-tuned software, unlike generic containers. Hooks bridge this gap by allowing containers to access these system-specific resources or enable custom features.
399
+
400
+
!!! info
401
+
This section outlines all hooks supported in production by the Container Engine.
402
+
However, specific Alps vClusters may support only a subset or use custom configurations.
403
+
For details about available features in individual vClusters, consult platform documentation or contact CSCS support.
404
+
392
405
[](){#ref-ce-cxi-hook}
393
406
### HPE Slingshot interconnect
394
407
@@ -489,19 +502,6 @@ The hook is activated by setting the `com.hooks.cxi.enabled` annotation, which
489
502
On most vClusters, the CXI hook for Slingshot connectivity is enabled implicitly by default or by other hooks.
490
503
Therefore, entering the enabling annotation in the EDF is unnecessary in many cases.
491
504
492
-
[](){#ref-ce-container-hooks}
493
-
## Container Hooks
494
-
495
-
Container hooks let you customize container behavior to fit system-specific needs, making them especially valuable for High-Performance Computing.
496
-
497
-
**What they do*: Hooks extend container runtime functionality by enabling custom actions during a container's lifecycle.
498
-
**Use for HPC*: HPC systems rely on specialized hardware and fine-tuned software, unlike generic containers. Hooks bridge this gap by allowing containers to access these system-specific resources or enable custom features.
499
-
500
-
!!! info
501
-
This section outlines all hooks supported in production by the Container Engine.
502
-
However, specific Alps vClusters may support only a subset or use custom configurations.
503
-
For details about available features in individual vClusters, consult platform documentation or contact CSCS support.
0 commit comments