-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Cache docker builds #3659
Cache docker builds #3659
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3659 +/- ##
=======================================
+ Coverage 90% 93% +3%
=======================================
Files 111 111
Lines 8011 8011
=======================================
+ Hits 7217 7448 +231
+ Misses 794 563 -231 |
@Borda I used Also, storing cache locally took more time when restoring the cache. So, does pushing cache images (separate images) to docker hub sound good to you? |
This pull request is now in conflict... :( |
1 similar comment
This pull request is now in conflict... :( |
This pull request is now in conflict... :( |
@Borda Shall we install nvidia-dali in this PR or in a later PR? |
I would keep it paired with the adding DALI example... |
hi @ydcjeff mind taking a look at failing tests? |
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.
lgtm, just wait till all CI passes
@Borda Before merging, just want to make sure this PR stores the cache metadata of the docker builds on docker hub with the separate names. |
how does it appear on Dockerhub, as a new entry/tag? |
It will appear as a new tag like You can see here for example: https://hub.docker.com/r/ydcjeff/pl/tags (this is just for testing this PR) |
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.
Great addition ! I didn't know about cache-from
and cache-to
. Really lean API from docker/build-push-action@v2
:) You have some small typos in the comment too.
author ydcjeff <ydcjeff@outlook.com> 1601049378 +0630 committer ydcjeff <ydcjeff@outlook.com> 1601469495 +0630 cache docker builds lock horovod at 0.19.5 done [ci skip] [CI SKIP] use --cache-from [ci skip] typo and horovod [ci skip] exclude pt 1.3 py3.8 [ci skip] conda no cache [ci skip] fix
I know 'Ready to go' is not meant to be added by PR author. But |
What does this PR do?
Fixes #3637 (comment)
Used
docker/build-push-action@v2
to able to cacheBefore submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃