Create a new tier-1 "container" site with dockerfiles for oneapi and gcc.#1915
Create a new tier-1 "container" site with dockerfiles for oneapi and gcc.#1915eap wants to merge 10 commits intoJCSDA:developfrom
Conversation
|
I'm good with these changes, but I wonder if it would be prudent to change the name to something more specific than "container" especially if/when other orgs add their own container-oriented configurations. |
eap
left a comment
There was a problem hiding this comment.
Thanks. PTAL. This will likely need some revision during release time but this seems like a good enough first-cut.
Fixes needed eventually:
- updated compilers.
- Remote clone with more targeted "copy" operations to improve chances for a docker build-cache hit.
climbfuji
left a comment
There was a problem hiding this comment.
I am happy with the changes, but I'll note @AlexanderRichert-NOAA's question about the naming convention. Maybe jedi-container or something else that describes the purpose better might work?
|
@alexrichert - good question on the naming. My goal here is to create tier1 spack-stack container site reusable by multiple parties; note that my instructions demonstrate the use of What are your thoughts on this; am I flying too close to the sun here or do you think this is achievable? One other thought is that since I'm using an ubuntu base and many platform config decisions are pegged to that, I could rename it |
From my side it's ok to merge this as |
|
@eap Since your PR doesn't touch any files used by CI, maybe add |
|
Yeah I'm fine with leaving it as "container" for now and we can rename later if/when needed. |
Add new tier-1 container site (configs/sites/tier1/container/) that will replace the legacy
configs/containers/spack-based container definitions for the 2.1 release.Motivation
The legacy container builds were a separate path from standard site configs and did not load modules or provide developer tools (without extensive post-build config modifications stretching and sometimes breaking the spack-container design intent). This brings containers under the tier-1 site model so they more closely match sites with loadable modules and pre-installed developer tools.
Checklist