This is an automated email from the ASF dual-hosted git repository.
slawrence pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/daffodil.git
The following commit(s) were added to refs/heads/main by this push:
new 27ec21b1b Ensure reproducible builds for daffodil release candidate
container
27ec21b1b is described below
commit 27ec21b1bce901162ac4c0a9d9676cb52da40fd0
Author: Steve Lawrence <[email protected]>
AuthorDate: Tue Jun 4 11:13:22 2024 -0400
Ensure reproducible builds for daffodil release candidate container
Update the daffodil release candidate container README to us a git URL
to the main daffodil branch to download the container source. This
ensures release candidate builds use the latest source and do not
include any local changes that could affect reproducibility.
Also add documentation how to to build, test, and remove local changes
since using a git URL makes that a bit more difficult.
DAFFODIL-2907
---
containers/release-candidate/README.md | 19 +++++++++++++++++--
1 file changed, 17 insertions(+), 2 deletions(-)
diff --git a/containers/release-candidate/README.md
b/containers/release-candidate/README.md
index 7659dd8e6..d69c760fb 100644
--- a/containers/release-candidate/README.md
+++ b/containers/release-candidate/README.md
@@ -21,9 +21,9 @@ To improve reproducibility and to minimize the effects and
variability of a
users environment, the Daffodil release container should be used to create
release candidates.
-To build the Daffodil release candidate container image:
+To build or update the Daffodil release candidate container image:
- podman build -t daffodil-release-candidate
/path/to/daffodil.git/containers/release-candidate/
+ podman build -t daffodil-release-candidate
https://github.com/apache/daffodil.git#main:containers/release-candidate
To use the container image to build a release run the following:
@@ -40,3 +40,18 @@ asked to verify the release files and, if everything looks
good, run a few
commands to push the release candidate out. Note that because the container
will use tools like git, gpg, and ssh, it is necessary to bind mount your local
configuration files into the container with the -v option.
+
+### Testing the Container
+
+To test changes made locally, use the following command to build the container:
+
+ cd /path/to/daffodi.git/containers/release-candidate
+ podman build -t daffodil-release-candidate .
+
+The same `podman run` command above can be used to run the container, but the
+`--dry-run` option should be appended to prevent publishing any results.
+
+When done, the container should be deleted to avoid accidentally using it for
+an official release:
+
+ podman image rm --force daffodil-release-candidate
