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

prune: move image pruning before build cache pruning #1527

Merged
merged 1 commit into from
Nov 21, 2018

Conversation

tiborvass
Copy link
Collaborator

This is cleaner because running system prune twice in a row
now results in a no-op the second time.

Signed-off-by: Tibor Vass tibor@docker.com

@tiborvass tiborvass force-pushed the fix-system-prune-filters branch 4 times, most recently from 72b7ba4 to db694fe Compare November 21, 2018 05:11
This is cleaner because running system prune twice in a row
now results in a no-op the second time.

Signed-off-by: Tibor Vass <tibor@docker.com>
@codecov-io
Copy link

Codecov Report

Merging #1527 into master will decrease coverage by 0.01%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master    #1527      +/-   ##
==========================================
- Coverage   55.23%   55.22%   -0.02%     
==========================================
  Files         289      289              
  Lines       19374    19384      +10     
==========================================
+ Hits        10702    10705       +3     
- Misses       7977     7983       +6     
- Partials      695      696       +1

Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

LOL, I thought that pruning cache before images was by design (as it generally completes faster, thus reducing the risk that prune times out / is canceled before the cache is pruned) 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants