From 7736337916538aab67a00739c53b8434da773a3b Mon Sep 17 00:00:00 2001 From: Graham Christensen Date: Thu, 20 Sep 2018 20:23:04 -0400 Subject: Clarfy the binary reproducibility problems of created=now with dockerTools.buildImage. --- doc/functions.xml | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) (limited to 'doc/functions.xml') diff --git a/doc/functions.xml b/doc/functions.xml index 31b40fb084a..0c0d82b0342 100644 --- a/doc/functions.xml +++ b/doc/functions.xml @@ -642,10 +642,12 @@ buildImage { Impurely Defining a Docker Layer's Creation Date - Because dates are an impurity, by default - buildImage will use a static date of one - second past the UNIX Epoch. This can be a bit frustrating when - listing docker images in the CLI: + By default buildImage will use a static + date of one second past the UNIX Epoch. This allows + buildImage to produce binary reproducible + images. When listing images with docker list + images, the newly created images will be listed like + this: - If you want to trade the purity for a better user experience, - you can set created to - now. + You can break binary reproducibility but have a sorted, + meaningful CREATED column by setting + created to now. and now the Docker CLI will display a reasonable date and sort the images as expected: - - + however, the produced images will not be binary reproducible. + -- cgit 1.4.1