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
# Exit with ENOENT 2 "No such file or directory", if the directory does not
179
-
# exist
172
+
# Exit with ENOENT 2 "No such file or directory", if the directory does not exist
180
173
if [ -d "${SPACK_CONFIG_DIR}" ]; then ln -s -r -v ${SPACK_CONFIG_DIR}/* ${SPACK_ROOT}/etc/spack/; else echo "${SPACK_CONFIG_DIR} does not exist!"; exit 2; fi
181
174
EOF
182
175
@@ -196,9 +189,19 @@ RUN ln -s ${SPACK_ROOT}/share/spack/docker/entrypoint.bash \
Copy file name to clipboardExpand all lines: containers/README.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,8 +8,6 @@ This folder contains the `Dockerfile` and `compose.*.yaml` files needed to build
8
8
9
9
Furthermore, those images download upstream compilers and common packages informed by the `upstream/[dev|prod]/[packages|compilers].spack.yaml` spack manifests.
10
10
11
-
Finally, there is a `spack-config` folder that contains a customised [spack-enable.bash](https://github.com/ACCESS-NRI/spack-config/blob/main/spack-enable.bash) used to load `spack`, as well as upstream compilers.
12
-
13
11
## How to build `spack` for testing
14
12
15
13
You can use spack in a similar way to `build-ci`, with it's own upstream `spack` used for compilers and common packages. This is also suitable for developers to test. Run the following Docker Compose commands:
@@ -26,4 +24,4 @@ When finished, you can run the following to shut down the services:
26
24
docker compose -f containers/compose.dev.yaml down --volumes
27
25
```
28
26
29
-
Users can modify `SPACK_PACKAGES_REPO_VERSION`/`SPACK_CONFIG_REPO_VERSION`, among other things, from within the docker compose file before running `docker compose build`.
27
+
Users can modify the `SPACK_CONFIG_REPO_VERSION`, among other things, from within the docker compose file before running `docker compose build`.
0 commit comments