-
Notifications
You must be signed in to change notification settings - Fork 24
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
Create GitHub Actions workflows to build and push Docker Images #212
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
overall looks good to me. it may be good to see if the build caches so that we don't rebuild all each time this workflow is run.
LGTM I don't think it will do any build caching since it will fire up a totally fresh instance each push. That shouldn't be a problem for dockerhub if the builds are deterministic, but it probably will waste some power. IIUC these images don't actually make use of anything in the repo other than the Dockerfiles themselves, so maybe something like...
|
Good idea. I was able to add a caching mechanism. For reference, here are the docs: |
Good idea. I have added the |
Proceeding with the merge here since all suggestions have been addressed. |
Hi @asmacdo, did you set an expiration date on Docker Hub for the
If the token is expired, I can replace the current one. Thanks. |
@kabilar I used a repo specific key, you'll need a new one. |
Thanks @asmacdo. All images have been built and pushed to Docker Hub. See latest GA run and images on Docker Hub. cc @satra |
@kabilar - thank you. as part of this should we disable autobuilds on dockerhub? |
Hi @satra, I disabled the autobuilds on dockerhub. I have noticed an issue with the GA builds. Only the |
Fix #141
main
DOCKERHUB_TOKEN
andDOCKERHUB_USERNAME
GitHub Actions secretsDockerfile
tag fromlatest
tolatest-base
Build configuration
on Docker Hub since we will now be pushing from GitHubcc @satra