Repository navigation
[release/2.2] Container site updates; move to new compilers and Ubuntu 26.04 - #2197
Merged
Merged
Conversation
…stack 2.2 Move configs/sites/tier2/aws-ubuntu2404 to configs/sites/tier1/aws-ubuntu. The site tracks the current Ubuntu LTS (26.04 as of 2.2) and is updated in place at each LTS instead of creating a new versioned site. Site config (derived from linux.default, verified to reproduce the built unified-gcc env hash-for-hash): - packages.yaml: Ubuntu 26.04 system externals (zlib excluded: the multiarch libdir breaks pmix's zlib detection), hand-written qt@5.15.18 external, jedi-python-env +bufrquery, and py-myst-parser@5: / py-sphinx@9: to avoid py-attrs/py-docutils duplicate splits from jedi-tools-env. - packages_gcc.yaml: gcc@14.3.0 via the -14 binaries (system default is gcc 15.2), mpi require openmpi@5.0.10. Drop all:prefer:%gcc, which acted as a dependency constraint and forced rebuilds of system externals. - packages_oneapi.yaml: oneAPI 2026.1.1 with +fix_rt_linkage, compiler flags pinning icx/icpx/ifx to the gcc-14 toolchain, gcc@14.3.0 companion, py-dask@2024.12.1 and met +graphics +shared-intel to avoid duplicates. - config.yaml: drop /tmp build_stage/cache overrides; /tmp on 26.04 is a RAM-backed tmpfs with quotas and fills during a unified-env build. README rewritten for 26.04: Lmod 8.7.60 from apt replaces the manual Lua/Lmod build, gcc-14 alongside the default gcc-15, uutils coreutils kept, llvm-14 dropped, build as the ubuntu user, module paths under envs/<env>/modules, met +lidar2nc/+modis unavailable with gcc 14 (common hdf-eos2 pin), and oneAPI notes (ulimit -s unlimited for jedi-bundle tests). Also update a stale aws-ubuntu2404 reference in tier2/ubuntu2404-nvhpc.
…ainer-ubuntu-2604
eap
marked this pull request as ready for review
October 30, 2026 15:15
ashley314
approved these changes
Oct 30, 2026
ashley314
left a comment
Collaborator
There was a problem hiding this comment.
Looks good, thank you!
8 of 37 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings the container site in line with tier1/aws-ubuntu for spack-stack 2.2. Ubuntu 26.04, GCC 14.3.0, OneAPI 2026.1.
Other changes:
load_jedi_bundle_env: for new meta-modules and some unexpected python odds and ends to fix the jedi build environment (as far as I can tell this is idiosyncratic to the container build; the base modules work better in the aws-ubuntu site, I will debug this issue later but for now the fixed loader enables successful jedi builds)Checklist