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/run.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,9 +83,7 @@ If an EDF is located in the search path, its name can be used in the `--environm
83
83
...
84
84
```
85
85
86
-
## Image Management
87
-
88
-
### Image cache
86
+
## Using container images
89
87
90
88
By default, images defined in the EDF as remote registry references (e.g. a Docker reference) are automatically pulled and locally cached.
91
89
A cached image would be preferred to pulling the image again in later usage.
@@ -101,6 +99,9 @@ To choose an alternative image store path (e.g., to use a directory owned by a g
101
99
!!! note
102
100
If the CE cannot create a directory for the image cache, it operates in cache-free mode, meaning that it pulls an ephemeral image before every container launch and discards it upon termination.
103
101
102
+
!!! note
103
+
Local container images are not cached. See the section below on how to use local images in EDF.
104
+
104
105
### Pulling images manually
105
106
106
107
To work with images stored from the NGC Catalog, please refer also to the next section "Using images from third party registries and private repositories".
0 commit comments