This repository has been archived by the owner on Dec 3, 2024. It is now read-only.
add spack config yaml and template to generate dockerfile #5
Conversation
This file contains 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
|
@rem1776 do I sill need to review this? |
|
@underwoo Yes this should still go in. |
|
@underwoo Actually on second thought, should we move the contents of this repository to hpc-me? Since it holds the FMS CI dockerfiles as well it'd probably be better to consolidate these files there. |
|
I'll merge this. If you do decide to migrate the container to the other project, we should probably close this project. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Updates to use a spack generated dockerfile. The dockerfile changes were generated with spack with the added yaml and template file. I included instructions for generating it in the yaml file.
As is it will download latest compatible versions for dependencies, but we can install any versions (or build options) available in spack via the config yaml.