-
Notifications
You must be signed in to change notification settings - Fork 57
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
Reproducibility: timestamp of /proc
changes when using bookworm?
#134
Comments
Ah, well, it's this coming back around, it seems. I had a quick patch in my internal Dockerfile for that (which was focal-based for different reasons and had this issue the last two years already). Copying it into the debuerreotype Dockerfile fixes the issue: |
It's not the whole story though. debootstrap versions are:
So apparently the issue skipped bullseye and/or version 1.0.123, but is present in both older and newer versions, but from what I see in the Git history (and trusting my past self to link the relevant commits in the MR-comment, glad there are any links at all), this behaviour should be unchanged since 1.0.107. |
😩 Is it possible something changed in |
First, I probably have to run a dedicated test with focal, because that patch is two years old. I knew the symptoms and it obviously fits together, but I have to be sure. Probably will be confirmed, though. Then we got debootstrap 1.0.126 in bullseye-backports, so I will try that as well. I really don't know what to expect. |
Some relief:
So it's between debootsrap 1.0.123 and 1.0.126. Precisely, here: https://salsa.debian.org/installer-team/debootstrap/-/commit/87cdebbcad6f4e16ba711227cbbbd70039f88752 |
I changed the image to bookworm to be able to build Ubuntu 22.04 images.
It seems that this host change breaks the reproduciblity of the images in a stupid-as-usual way:
/proc
gets a different mtime (from a buster-image):Where the green line is from the image built on bullseye. The mtime of the bookworm image corresponds to the
InRelease
timestamp (I build debian from live repos with--non-debian
), so this is done bydebuerreotype-fixup
. The older time is from thedata.tar.xz
in thebase-files
package.I don't see why bookworm would modify /proc, but bullseye would not. If bullseye would modify /proc, I'd expect it to be moved back to
$epoch
as well. Any ideas?The text was updated successfully, but these errors were encountered: