fix: container cleanup #618
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
bugfix
AtomicFS
force-pushed
the
fix/container-cleanup
branch
4 times, most recently
from
2a1e6f1 to
b481b0f
Compare
github-actions
bot
added
documentation
- run weekly - also keep discontinued containers clean Signed-off-by: AtomicFS <[email protected]>
Signed-off-by: AtomicFS <[email protected]>
AtomicFS
force-pushed
the
fix/container-cleanup
branch
from
74c2b24 to
ff93c58
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have not seen or heard any problems related #549, so I think we turn the cleanup on again, but this time as separate workflow (see #536).
Discontinued containers did get rather messy, for
linux_6.1.45we had over 30 un-tagged images (not anymore since I ran this manually).I do see warnings on
coreboot_4.20andcoreboot_4.22, but that is because there is no such package / container anymore (I suspect that we switched tocoreboot_4.20.1andcoreboot_4.22.01faster than we make releases, and maybe overzealous cleanup removed them? Not sure. But it is only warning on discontinued container, so I don't really care.