Replies: 2 comments
-
|
Hello I think your diagnosis is correct. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for the delay. If you're starting with the contents in What's your use case here? In general, we utilize apptainer for all of our builds (both for CI/CD and deployment on HPC resources). I would like to in time transition those builds to docker (as we can easily port docker -> apptainer), but it isn't on the priority list at the moment. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Building MOOSE in Custom Docker Image
Hello Moose Community and specifically @loganharbour
My goal is to build a MOOSE docker image based on the provided Dockerfile with my own base image and custom PETSc options. I saw there was discussion of deprecating the docker file but the infrastructure I work with needs a Docker Image. I can build my own and maintain it once I get it going.
However, I'm having trouble building MOOSE with no custom options. I get a huge log of C++ compile errors like this:
I get errors with the
releaseandnextbranches and no changes or additional options besides my own image for the base which is just a relatively bare bones Ubuntu Focal image.I believe this is due to a mismatch between the version of MOOSE I am using and Libmesh which is set by a SHA in the docker container.
I can update the Libmesh reference but in general how do I find a SHA to pin which will work with the current version of MOOSE?
Thank you!
My Image
Diagnostics
Running the docker container after the failed compile to see the status:
`diagnostics.sh` output
libMesh configure log
Compile error logs
Beta Was this translation helpful? Give feedback.
All reactions