upgrade e3sm-imgs to 0.0.9 and add singularity2 machine #6519
Conversation
|
mahf708
changed the title
mahf708
force-pushed
the
mahf708/idp/e3sm-imgs-v0.0.7
branch
from
00bb9a1 to
767332e
Compare
| container: | ||
| image: ghcr.io/mahf708/e3sm-imgs:v0.0.6 | ||
| image: ghcr.io/mahf708/e3sm-imgs:v0.0.9 |
There was a problem hiding this comment.
Can we move these images to an E3SM account?
There was a problem hiding this comment.
Yes.
I was planning of moving the entire "e3sm-imgs" repo (or we can rename it) to E3SM-Project once we cross the 0.1.0 version threshold. There's only substantial one item on my todo list before reaching the 0.1.0: making an intel container (cpu). There's also one logistical point I would like to address (saving less of the intermediate "test"-tagged containers, which I could do in one PR soon).
Do you prefer I address these two items before integrating this PR or in a subsequent PR?
Alternatively, I can also upload these images directly to the E3SM Docker account from my repo, though I think we should have the repo be under E3SM-Project sooner or later.
There was a problem hiding this comment.
The other thing you will notice is that I opted to introduce "singularity2" temporarily because I didn't want to mess up the circleci workflow (I will reunite the two singularities soon, but I am trying to focus on getting the intel container as well as some basic runtime/production container going...)
A significant update in the underlying container image we are using for the "gh" testing suite. These updates primarily include moving to a spack-based installation/building of key tools. The container is now based on ubuntu 22.04 (apr 2022) with gcc 11 (the default gcc compilers for ubuntu 22.04). This update is the first step towards operationalizing these containers (with different varieties, e.g., oneapi compilers, etc.) for production-grade runs. Relevant changes in container repo: mahf708/[email protected] [BFB]
A significant update in the underlying container image we are using for the "gh" testing suite. These updates primarily include moving to a spack-based installation/building of key tools. The container is now based on ubuntu 22.04 (apr 2022) with gcc 11 (the default gcc compilers for ubuntu 22.04). This update is the first step towards operationalizing these containers (with different varieties, e.g., oneapi compilers, etc.) for production-grade runs.
Relevant changes in container repo: mahf708/e3sm-imgs@v0.0.6...v0.0.9