feat: Strip timestamps from base images#10331
Open
Bownairo wants to merge 2 commits into
Open
Conversation
Bownairo
added
the
CI_PUSH_BASE_IMAGE
Bownairo
force-pushed
the
eero/base-image-timestamps
branch
5 times, most recently
from
e6dbb53 to
2d323c4
Compare
Bownairo
force-pushed
the
eero/base-image-timestamps
branch
from
2d323c4 to
b3bff06
Compare
basvandijk
approved these changes
May 28, 2026
Bownairo
commented
May 28, 2026
Comment on lines
+82
to
+83
| # NOTE: This does not touch base layers. As base images are currently built | ||
| # by Docker, not podman, they leak timestamps. (This doesn't really matter, |
Contributor
Author
There was a problem hiding this comment.
container-base-images.yml does not go through the same build path as build_container_base_image.py, so it's not quite as hermetic, and might give different results than local builds. The whole thing isn't reproducible anyway, which is why we use pinned containers, but it might be nice to get them on the same build path.
It's probably just as much work to remove the base images entirely, which would be a better route.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
From the fallout of #10208
The new podman seems to be able to wrap more timestamps coming from base images (back to epoch), which leads to cache pollution across the upgrade to 26.04. To avoid this, we clear all timestamps before creating cached artifacts, and make some first steps to removing timestamps from the base images entirely.