Docker builds no longer come with mpich version/.sif releases

[nietzscheanmonkey]

It appears that the idaholab/moose-dev:latest image no longer comes with mpich, only open-mpi. The last container to come with mpich is https://hub.docker.com/layers/idaholab/moose-dev/e930b1d/images/sha256-9e425c2df00f4a80f902a2e1672de06ecfbfaadb4c64281d77083e5471c4bc53

Is this an intentional permanent change, or an oversight?

Additionally, #27377 indicates that .sifs may be made available. Is this still happening?

@loganharbour

[loganharbour]

Is this an intentional permanent change, or an oversight?

It is intentional. Our default build is with openmpi, so that's what we're publishing. This is what we use for all of our app releases. If there's a need for the docker mpich image, let me know and we can release that too.

Additionally, #27377 indicates that .sifs may be made available. Is this still happening?

It's on the list. Do you have a more immediate need?

[nietzscheanmonkey]

Our stack currently uses mpich, so it would be preferred. If it can be released trivially, it would be appreciated.

Re: the sifs, as of right now it looks like Singularity is our preferred solution over docker. It's not a giga-blocker, as I can still convert between the OCIs and run the ./environment script, but if releasing sifs could be pushed up the priority list on the backlog, it would definitely be helpful.

[milljm]

Standing up services in our DMZ is usually the blocker. Being that these images are of open source nature, if we could push to a public service already in existence that would be nice to know about. Do you prefer one over the other/know of any?

[loganharbour]

Do you prefer one over the other/know of any?

Luckily, we can actually use docker hub for publishing arbitrary oras artifacts (i.e., apptainer/singularity images). I just haven't gotten around to this yet because it'll require some more infrastructure scripting.