Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Container #678

Merged
merged 12 commits into from
Sep 16, 2024
Merged

Container #678

merged 12 commits into from
Sep 16, 2024

Conversation

aradhakrishnanGFDL
Copy link
Collaborator

Description
Container build in GitHub actions workflow, an accompanying Dockerfile also pushed.

How Has This Been Tested?
Tested at GFDL using podman. Local test instructions passed to @jtmims. Works on synthetic data and example POD. Works partially on forcing feedback, but replicates non-container workflow. Open to more tests and documentation.

@aradhakrishnanGFDL aradhakrishnanGFDL marked this pull request as draft August 30, 2024 16:50
@wrongkindofdoctor wrongkindofdoctor added feature-request New feature or request containers Podman, Singularity, and Docker containers labels Sep 3, 2024
@jtmims jtmims self-assigned this Sep 4, 2024
@jtmims
Copy link
Collaborator

jtmims commented Sep 4, 2024

Great news @aradhakrishnanGFDL! I was able to pull the docker package from the github repository and launch on my windows machine. Inside, I was able to run the example_multicase POD on some synthetic data, and it ran and plotted. It's functional! It's really cools seeing a container working on some data! I did have some trouble with tracking down micromamba/conda env related paths, but that is something that could be cleared up with some docs.

@aradhakrishnanGFDL
Copy link
Collaborator Author

@wrongkindofdoctor do you prefer merging this into main, or maintain a separate container branch until things seem to be working as expected? There is a CI workflow that builds a docker image and pushes to GitHub.io registry. It does not seem harmful to have it merge into main, except tests for the container as part of CI are not in right now.

@aradhakrishnanGFDL
Copy link
Collaborator Author

@jtmims @wrongkindofdoctor I tested the workflow with another PR that pushes to a container branch.

Here is the actions workflow -

https://github.com/NOAA-GFDL/MDTF-diagnostics/actions/runs/10891122710/job/30221357884

@jtmims you can now use this for the docs instead my ghrc.io pointers. Hope this helps.

https://github.com/noaa-gfdl/MDTF-diagnostics/pkgs/container/mdtf-diagnostics

@aradhakrishnanGFDL aradhakrishnanGFDL marked this pull request as ready for review September 16, 2024 20:10
@aradhakrishnanGFDL
Copy link
Collaborator Author

@wrongkindofdoctor do you prefer merging this into main, or maintain a separate container branch until things seem to be working as expected? There is a CI workflow that builds a docker image and pushes to GitHub.io registry. It does not seem harmful to have it merge into main, except tests for the container as part of CI are not in right now.

I have a container branch created. You can delete it as you see fit. I am okay with this PR being merged into main, in any case. I leave it to you and @jtmims.

@wrongkindofdoctor wrongkindofdoctor merged commit 9d4aab8 into NOAA-GFDL:main Sep 16, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
containers Podman, Singularity, and Docker containers feature-request New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants