Singularity installation

[Jonathan]

I have installed singularity and singularity-ohpc on both my master node and my compute nodes.  It works as expected on the master node.  Singularity itself runs on my compute nodes, but there is no squashfs in the running kernel as shown by /proc/filesystems.  squashfs-tools 4.3-0.21 is already on both master and compute nodes (according to yum).

Does anybody see what I'm doing wrong?  TIA! 

[Jason Stover]

You probably don't have the full kernel-modules package installed in
the compute image, so add `squashfs` as a module to be added into the
bootstrap and rebuild it.

Just to cover filesystems you could add in a:

drivers += kernel/fs/

-Jason

On Wed, Oct 13, 2021 at 2:18 PM Jonathan <j...@newtrumpet.org> wrote:
>
> I have installed singularity and singularity-ohpc on both my master node and my compute nodes. It works as expected on the master node. Singularity itself runs on my compute nodes, but there is no squashfs in the running kernel as shown by /proc/filesystems. squashfs-tools 4.3-0.21 is already on both master and compute nodes (according to yum).
>
> Does anybody see what I'm doing wrong? TIA!
>

> --
> You received this message because you are subscribed to the Google Groups "Warewulf" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to warewulf+u...@lbl.gov.
> To view this discussion on the web visit https://groups.google.com/a/lbl.gov/d/msgid/warewulf/114179c4-e5c0-4994-8dd8-eee5711ebfdfn%40lbl.gov.

[Gregory M. Kurtzer]

Just a note,... Warewulf 4 doesn't require changing bootstrap.conf to add kernel modules.

Also, the 4.2.0 rc1 has been tagged and released.

To view this discussion on the web visit https://groups.google.com/a/lbl.gov/d/msgid/warewulf/CAGfAqt-ta7JgVcjie7WF1GtmLewjHzH1DYm4%2BDzWmjwRZKmn%3Dg%40mail.gmail.com.

--

Gregory M. Kurtzer

CEO, CIQ: http://ctrliq.com

Director, The Rocky Enterprise Software Foundation: http://www.rockylinux.org

[Gregory M. Kurtzer]

Real quick question, are you currently running Warewulf v3? If so, I believe the file you would want to edit would be in the warewulf system config dir (e.g. /etc/warewulf/bootstrap.conf) but that is of course dependent on the configure options you compiled with (e.g. --prefix). If it was installed via RPM, it should be in /etc/warewulf/bootstrap.conf. Once edited, you will need to run wwmkbootstrap again for that kernel.

Regarding forcedeth, I don't see that even available in the Rocky8 kernel (which is the same as CentOS and RHEL). Is forcedeth still supported in more recent kernels?

On Thu, Oct 14, 2021 at 7:44 AM Jonathan <j...@newtrumpet.org> wrote:

I added drivers += kernel/fs/ and modprobe += squashfs into /etc/bootstrap.conf and then rebuilt it with the wwbootstrap command.  Not only is there no squashfs, but  I now have fewer drivers than I did before!  Perhaps I also need to follow up with the wwvnfs command...  And per our earlier conversation, I never got forcedeth in their either, so my 12-core nodes are still offline.  They worked great on perceus!

And speaking of perceus, thank you Greg for coming out with ww4.  Do you have any plans for the old ww2 monitoring commands, such as wwtop or wwnodes?  I found those commands very handy, along with the perceus commands such as "perceus node status".  Those commands prevented me from making dumb mistakes as I am probably making right now.