Skip to content

Commit

Permalink
update README with instructions for flux rocky
Browse files Browse the repository at this point in the history
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
  • Loading branch information
vsoch committed Apr 7, 2023
1 parent 03c7146 commit 14b3779
Showing 1 changed file with 18 additions and 6 deletions.
24 changes: 18 additions & 6 deletions spack-rocky-libfabric/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,13 @@ $ docker run -it ghcr.io/rse-ops/spack-rocky-libfabric:tag-8 bash
```

The entrypoint sources spack at `/opt/spack-environment` so you don't need to worry
about that. Flux should be on the path, so we can start a test instance:
about that. Since we shouldn't run flux as root, let's create a shell as user "flux"

```bash
$ sudo -E -E HOME=/home/flux -u flux /bin/bash
```

Flux should be on the path, so we can then start a test instance:

```bash
$ flux start --test-size=4
Expand All @@ -23,23 +29,29 @@ $ flux start --test-size=4
And then try submitting a job!

```bash
$ flux mini run hostname
$ flux run hostname
```
```console
633f87d7ebb8
```

To see the versions of dependencies we have installed, spack to the rescue!
Check out the spack lockfile (in the concrete specs section toward the top):

```bash
$ cat /opt/spack-environment/spack.lock | less
```

Here is a quick summary of versions (on Rocky Linux 8):
Here is a quick summary of versions (on Rocky Linux 8) for stuff we care about:

```
openmpi: 4.1.2
gcc: 8.5.0
libfabric: 1.14.0
flux-core: 0.44.0
flux-core: 0.49.0
flux-pmix: 0.2.0
flux-sched 0.25.0
flux-sched 0.27.0
```

Note that you could start the flux instance as root, and you'd see a jobtap
plugin error (which largely can be ignored) but you really shouldn't be running
as root :)

0 comments on commit 14b3779

Please sign in to comment.