Bootstrap images from Spack

[haampie]

In https://github.com/haampie/spack-docker-bootstrap/ I've created a simple example where Spack's own dependencies are installed with Spack.

That way we can get better performance, and we have a slightly cleaner environment (not too much stuff in /usr that gets picked up during the build).

• Who's managing this repo? @scottwittenburg?
• How are images pushed?

[scottwittenburg]

Looking at the short commit history, this repo was set up by @alalazo (IIRC based on some Dockerfiles at UO/OACISS repo). Also based on that commit history, I'm not sure you could say anyone is "managing" it 😜

Looks like images are built and pushed as part of the workflow here.

[scottwittenburg]

Your idea sounds reasonable to me, or more likely I just trust you. So what you could do is push some of those images to some container registry and make a spack PR to make some stacks use them. What do you think?

[alalazo]

If I recall correctly, I used this repo as a proof of concept to show how we could generate images automatically in CI for the pipelines. E4s related images are still being generated elsewhere, I think here: https://github.com/UO-OACISS/e4s

[alalazo]

How are images pushed?

gitlab-runners/.github/workflows/containers.yml

Lines 73 to 81 in d0fb9ec

	- name: Build & Deploy ${{ matrix.dockerfile[1] }}
	uses: docker/build-push-action@v2
	with:
	file: Dockerfiles/${{matrix.dockerfile[1]}}
	platforms: ${{ matrix.dockerfile[2] }}
	push: ${{ github.event_name != 'pull_request' }}
	tags: |
	ghcr.io/spack/${{ env.container }}
	ghcr.io/spack/${{ env.versioned }}

[haampie]

I'm gonna close this since #59 effectively does this.