-
Notifications
You must be signed in to change notification settings - Fork 235
Fix ImageStore.prune() behavior to actually remove images #420
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
Fix ImageStore.prune() behavior to actually remove images #420
Conversation
|
making cleanupOrphanedBlobs public because we'll need it in container as well |
|
Could this be handled without any changes to Containerization? That is to say:
|
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.
See above comment. I guess we would need to make cleanOrphanedBlobs() public for image prune but could we do the image pruning completely in container-apiserver?
Yeah like we discussed, we basically rename |
Sync with Apple's containerization repo (57 commits behind). Notable upstream changes: - LinuxContainer: "Harden" stop (apple#388) - OCI runtime support (apple#416) - Memory threshold monitoring (apple#427) - FileHandle option for serial console (apple#410) - Keep reference to vended execs (apple#408) - Sync(2) on shutdown (apple#400) - Fix ImageStore.prune() behavior (apple#420) - Various stability improvements Resolved conflicts: - LinuxContainer.swift: Merged bootLog type change with our useNetworkNamespace - Application.swift: Kept our service startup code (removed old log line per upstream) - Server+GRPC.swift: Used upstream's async ManagedContainer, kept our DNS comment
ImageStore.prune()doesn't remove unreferenced images #417.Rename
_prune()tocleanupOrphanedBlobs()to clarify what it actually does, and removeprune()method as we'll do all that logic in container directly.