-
Notifications
You must be signed in to change notification settings - Fork 113
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
Clean up old habitat packages on upgrade #6635
Comments
Example of customer communications for manual cleanup: https://github.com/chef/customer-bugs/issues/566#issuecomment-1023675551 |
This popped up in my github notifications for some reason and since I'm here, I thought I would mention that changing
automate/components/automate-deployment/pkg/depot/garbage_collect.go Lines 68 to 73 in a8aad69
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When Automate is upgraded and dependencies are upgraded, additional copies of the dependencies may be left behind. As these dependencies age, they may be detected by customers vulnerabilities scanners and cause additional reporting and remediation work for the customer. We should clean up unused old packages from disk.
Keep in mind that automate prevents other services from running in it's habitat supervisor, but that a system may have a separate habitat supervisor running using the same
/hab
filesystem. See #455 and #2478.hab pkg uninstall
does have a--keep-latest n
flag that keeps at least n copies of a package, and won't uninstall packages that are dependencies of others. Something like this works, but don't do this:The text was updated successfully, but these errors were encountered: