You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should expose commit-timestamp as SOURCE_BUILD_EPOCH in all of our tasks. Not all tools respect that, but it is the standard environment variable that they should respect.
Notably, buildah doesn't respect it, but it does accept a --timestamp argument that will help produce the same bits, assuming that nothing inside the containerfile being built is not sensitive to the time.
We should also provide a --build-arg SOURCE_BUILD_EPOCH=$SOURCE_BUILD_EPOCH to each buildah build, so that if a containerfile accepts that as an ARG, it can take advantage of that.
Doing these things won't give us all 100% bit-wise reproducible builds, but it will close some gaps in that direction.
The text was updated successfully, but these errors were encountered:
ralphbean
changed the title
Use commit-timestamp in buildah task in pursuit of reproducible builds
Use commit-timestamp in tasks in pursuit of reproducible builds
Aug 8, 2024
There are lots of challenges to producing bit-wise reproducible builds. One of them is to get all tools all the way through the build chain to use the same time. See https://reproducible-builds.org/docs/ and in particular https://reproducible-builds.org/docs/source-date-epoch/
--timestamp
argument that will help produce the same bits, assuming that nothing inside the containerfile being built is not sensitive to the time.--build-arg SOURCE_BUILD_EPOCH=$SOURCE_BUILD_EPOCH
to each buildah build, so that if a containerfile accepts that as an ARG, it can take advantage of that.Doing these things won't give us all 100% bit-wise reproducible builds, but it will close some gaps in that direction.
The text was updated successfully, but these errors were encountered: