Port docker build workflow to github

[glemieux]

Tasks

Preview Give feedback

1. Setup docker secret keys
2. jupyterlab docker image build workflow #16
   +0
3. baseos docker image build workflow #15
   2 of 2
   +0
4. elm-fates docker image build workflow #14
   +0
5. tutorial data container build workflow #17
   0 of 2
   +0
6. Develop pull request testing methodology

[glemieux]

What particularly behavior do we want to test within each container, particularly for containers that build on each other? Should testing be conducted only for pull requests or also for merges to main?

baseos:

• test build elm-fates dockerfile off of new image
• test tooling (e.g. nco package, python scipy and netcdf4 installs)
• test applications built from source (xml parser, hdf5, netcdf, openMPI)

elm-fates:

• can we build a simple single site case (see e3sm testing for examples to adopt)

jupyter:

• minimum exercises for installed packages

[glemieux]

• Question: do docker hooks affect the github image build?
• Review how the docker buildx action works

[glemieux]

Note that the docker actions currently don't work with the macos-14 github arm64 runners: see docker/actions-toolkit#317. It might be possible to use the "large" linux arm runners, but those are only available to Github Team or Enterprise plans: https://docs.github.com/en/actions/using-github-hosted-runners/using-larger-runners/running-jobs-on-larger-runners.

Given the above, until this rolls out for more plans or hardware virtualization is provided for the macos arm runners, this will have to be build with docker's platform emulation.