Reproduced OCI images (Was: repro-env: Documented and reproducible build environments)

Wolf Vollprecht w.vollprecht at gmail.com
Mon Apr 28 16:41:44 UTC 2025


Interesting work! This is very similar to what we are doing in
`rattler-build` where we are storing essentially a lockfile of everything
that went into the "build" and "host" environments used at build-time to
build a given Conda package (https://rattler.build/latest/rebuild/).

We do it using `conda` packages that are generally stored forever so
rebuilding should be possible (if the software allows, of course).


Am Mo., 28. Apr. 2025 um 17:16 Uhr schrieb cen <imbacen at gmail.com>:

> > If there's a tool to wrap a single statically linked binary (that I
> > built with repro-env) into an OCI image I would be very curious to
> > know about this tool, but I'm still not sure that would give you "bit
> > for bit identical reproducible builds" in the traditional sense, as
> > soon as you introduce "push and pull from a registry".
>
> I guess building the (static) binary with repro-env and then just copy
> it into a runtime image does help in a sense that you don't need to mess
> around with stage 1 build and setting up the env properly. It's not
> pretty though.
>
> Base image might not be reproducible (yet) but that's a different
> problem. It seems this has progressed quite a bit in the past few years
> so it'll happen eventually.
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.reproducible-builds.org/pipermail/rb-general/attachments/20250428/262559da/attachment.htm>


More information about the rb-general mailing list