Merge pull request #86 from benkirk/container_update

reorg of containers based on review feedback
NCAR · Dec 14, 2023 · 7fc72f4 · 7fc72f4
2 parents 1dc183b + 15ac91f
commit 7fc72f4
Show file tree

Hide file tree

Showing 5 changed files with 169 additions and 186 deletions.
diff --git a/docs/environment-and-software/user-environment/containers/examples.md b/docs/environment-and-software/user-environment/containers/examples.md
@@ -281,7 +281,7 @@ With the container built from the steps above (or simply pulling the resulting i
 
     - We make use of the `--bind` argument first to mount familiar GLADE file systems within the container,
 
-    - and again to "inject" the host MPI into the container (as described [here](./running_containers.md#running-containerized-mpi-applications)).  The `/run` directory necessity is not immediately obvious but is used by Cray-MPICH as part of the launching process.
+    - and again to "inject" the host MPI into the container (as described [here](./working_with_containers.md#running-containerized-mpi-applications)).  The `/run` directory necessity is not immediately obvious but is used by Cray-MPICH as part of the launching process.
 
     - We also need to use the `--env` to set the `LD_LIBRARY_PATH` inside the image so that the application can find the proper host libraries.  Recall when we built the FastEddy executable in the containerized environment it had no knowledge of these host-specific paths.  Similarly, we use `--env` to set the `LD_PRELOAD` environment variable inside the container.  This will cause a particular Cray-MPICH library to be loaded prior to application initialization.  This step is not required for "bare metal" execution.
 

diff --git a/docs/environment-and-software/user-environment/containers/index.md b/docs/environment-and-software/user-environment/containers/index.md
@@ -63,7 +63,7 @@ To support these needs users must:
 
 -  Run specialized containers within a single node as part of an analysis workflow.
 
-We address all of these use cases in our discussion of [building](./building_containers.md) and [running](./running_containers.md) containers.  Additionally we provide a collection of containerized workflow [examples](./examples.md) building upon this reference foundation.
+We address all of these use cases in our discussion of [working with containers](./working_with_containers.md).  Additionally we provide a collection of containerized workflow [examples](./examples.md) building upon this reference foundation.
 
 
 ---

diff --git a/docs/environment-and-software/user-environment/containers/running_containers.md b/docs/environment-and-software/user-environment/containers/running_containers.md
-Original file line number
+Diff line change
@@ Expand Up / @@ -63,7 +63,7 @@ To support these needs users must: @@
     -  Run specialized containers within a single node as part of an analysis workflow.
-    We address all of these use cases in our discussion of [building](./building_containers.md) and [running](./running_containers.md) containers.  Additionally we provide a collection of containerized workflow [examples](./examples.md) building upon this reference foundation.
+    We address all of these use cases in our discussion of [working with containers](./working_with_containers.md).  Additionally we provide a collection of containerized workflow [examples](./examples.md) building upon this reference foundation.
     ---
@@ Expand Down @@