Update Image Update Policy to include monthly rebuild clause #5868
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
mthalman
approved these changes
Sep 10, 2024
mthalman
approved these changes
Sep 10, 2024
MichaelSimons
approved these changes
Sep 10, 2024
mthalman
approved these changes
Sep 10, 2024
Do you mean Ubuntu chiseled images? |
richlander
approved these changes
Sep 11, 2024
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.
Our current Image Update policy specifies that we only force re-build for base image updates and CRITICAL severity CVEs. Ubuntu Chiseled images are made from
scratch, so that never happens. In the case where .NET servicing skips a month, that leaves Chiseled users with no updates for two whole months. Since Ubuntu Chiseled has limited support for extending or updating images (#4811, canonical/chisel#118), that leaves users without any action to take to resolve any HIGH or lower severity CVEs that have been disclosed since the last re-build.In practice, this hasn't been a huge issue because Chiseled images inherently have a much smaller attack surface than other images we publish. However, it's still a scenario which can and does happen, so we should account for it.
Rebuilding all images every month regardless of whether there's a .NET release is a reasonable compromise for this scenario. This should be a temporary measure until #4811 is better supported.
/cc @richlander