From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Unreproducible «When Docker images become fixed-point»?
Date: Tue, 05 Jul 2022 09:44:37 +0200 [thread overview]
Message-ID: <878rp86m1m.fsf@inria.fr> (raw)
In-Reply-To: <86o7y4xyjp.fsf@gmail.com> (zimoun's message of "Tue, 05 Jul 2022 01:12:26 +0200")
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
>> A possible reason why we’re building a different derivation than back
>> then is provenance info: as explained under ‘--save-provenance’ in the
>> manual, provenance info is not “canonical” and we could end up including
>> different provenance info. I don’t have any clear scenario in mind but
>> that sounds plausible.
>
> I do not understand why provenance is not deterministic. I mean I
> understand that two provenances can build the same pack, but I miss why
>
> guix time-machine -C channels.scm \
> -- pack -f docker --save-provenance -m manifest.scm
>
> is not building the same pack for the exact same channels.scm and
> manifest.scm files. Why the resulting provenance info should be
> different?
I don’t know either, but that’s the only plausible scenario I can think
of. We would need the original .drv or the original pack to compare.
> Maybe there is bug in how the provenance is managed; but I do not think
> it comes from this part. Instead, I vaguely think the bug is from
> elsewhere – dependent on filesystem or unsorted list or other creative
> ideas. :-)
No, no: the store file names differ. That means we’re building
different derivations in the first place.
> Well, let save some data, replay this scenario 6 months later and
> investigate. :-) Keep you in touch.
Yeah.
Another approach is to take the derivation returned by
guix time-machine --commit=fb32a38db1d3a6d9bc970e14df5be95e59a8ab02 -- \
pack -f docker --save-provenance python python-numpy -d
and to look for things that might vary between invocations or call
sites: provenance data, imported modules, (guix config) details,
whatever.
Thinking about it, (guix config) is one possible source of discrepancy:
it captures sysconfdir and localstatedir, so you’ll get a different
result if you have different settings. The defaults are:
(define-public %localstatedir "/var")
(define-public %sysconfdir "/etc")
Could it be that you had something different back then?
Ludo’.
next prev parent reply other threads:[~2022-07-05 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 17:03 Unreproducible «When Docker images become fixed-point»? zimoun
2022-07-04 13:37 ` Ludovic Courtès
2022-07-04 23:12 ` zimoun
2022-07-05 7:44 ` Ludovic Courtès [this message]
2022-07-05 10:38 ` zimoun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rp86m1m.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.