* Reproducible Containers Paper
@ 2023-01-09 1:56 Carl Dong
2023-01-17 15:53 ` Ludovic Courtès
0 siblings, 1 reply; 2+ messages in thread
From: Carl Dong @ 2023-01-09 1:56 UTC (permalink / raw)
To: guix-devel
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
Hi all,
I came across a paper that might be of interest to the Guix community.
The paper is titled "Reproducible Containers”: https://dl.acm.org/doi/pdf/10.1145/3373376.3378519, featured by Meta in their post: https://developers.facebook.com/blog/post/2022/11/22/hermit-deterministic-linux-testing/
I was thinking about this in terms of how to have timestamp reproducibility inside Guix build containers which has been a problem in the past for building from source, their approach in 5.3 is interesting (but perhaps a bit invasive).
There are also discussions of:
1. Reproducible randomness (haha)
2. Reproducible scheduler
3. etc.
Cheers,
Carl Dong
[-- Attachment #2: Type: text/html, Size: 1193 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Reproducible Containers Paper
2023-01-09 1:56 Reproducible Containers Paper Carl Dong
@ 2023-01-17 15:53 ` Ludovic Courtès
0 siblings, 0 replies; 2+ messages in thread
From: Ludovic Courtès @ 2023-01-17 15:53 UTC (permalink / raw)
To: Carl Dong; +Cc: guix-devel
Hi Carl,
Carl Dong <contact@carldong.me> skribis:
> The paper is titled "Reproducible Containers”: https://dl.acm.org/doi/pdf/10.1145/3373376.3378519, featured by Meta in their post: https://developers.facebook.com/blog/post/2022/11/22/hermit-deterministic-linux-testing/
Interesting! Probably a sledgehammer for reproducible builds… except
perhaps for timestamp issues, as you write.
> I was thinking about this in terms of how to have timestamp reproducibility inside Guix build containers which has been a problem in the past for building from source, their approach in 5.3 is interesting (but perhaps a bit invasive).
Yes, this bit is interesting:
To ensure airtight interception of vDSO calls, DetTrace instead, just
after each execve system call, replaces the vDSO library code with our
implementation where each vDSO function makes a direct system
call—which is duly intercepted via ptrace. We furthermore make the
vvar page unreadable to prohibit any access to the raw
nondeterministic data that vDSO timing calls use.
I wonder what this entails exactly, and whether one needs to ptrace
every single process to intercept exec calls in child processes, which
would be prohibitive.
Thanks for sharing!
Ludo’.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-01-17 15:53 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-09 1:56 Reproducible Containers Paper Carl Dong
2023-01-17 15:53 ` Ludovic Courtès
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).