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

Improve docker in docker cleanup #6105

Closed
BenTheElder opened this issue Dec 28, 2017 · 5 comments
Closed

Improve docker in docker cleanup #6105

BenTheElder opened this issue Dec 28, 2017 · 5 comments
Assignees
Labels
area/images priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@BenTheElder
Copy link
Member

Working on this today so we can more freely enable dind (along with #5436), in short:

  • Move cleanup code out of bash so we can write something more sophisticated
  • Implement more robust cleanup of images we aren't trying to cache.
    • We want to keep pulled base images around to reduce flakiness, but not built images

To implement more robust cleanup:

  • We can't reliably detect if an image was pulled, but we can tell how old an image is. Base images should typically become old (say, older than 1 week), built images should not.
    • Pro: simple, catches images with tags we haven't hard-coded (unlike say, kube-build)
    • Con: we could let images slip if cleanup fails to run on a node for too long after a build. This could probably be solved in the future by periodically flushing ALL cache on the node. xref improve caching on prow #5436

/area images
/priority important-soon
/assign

@k8s-ci-robot k8s-ci-robot added area/images priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Dec 28, 2017
@BenTheElder
Copy link
Member Author

FYI @rramkumar1 I think we can enable dind for your job and then follow-up with this. We'll try setting up ingress-gce with it's own data root at least.

@rramkumar1
Copy link
Contributor

@BenTheElder SGTM

@BenTheElder
Copy link
Member Author

fixed in #6106

we might want to do some follow-ups though

@BenTheElder
Copy link
Member Author

This works (#6106 (comment)), but it's not complete. We should also sometimes clean up older images, eg some 10 day old kubemark stuff falls through now because it's older than the threshold.

We could randomly delete all images with a low probability 🤔

@BenTheElder
Copy link
Member Author

/close

Will open a new issue if we have problems, the current behavior is pretty great for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/images priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

3 participants