Docker cached image for dmaketgz may result in wrong release date set

[andrewkirillov-ibm]

I did this

Few weeks ago (Nov 13th) I created release packages using ./scripts/dmaketgz <version> as mentioned in RELEASE-PROCEDURE.md

I then created new packages today following same procedure. While the script (docker container) was running it reported:

datestamp 2024-11-13

Checking curlver.h from the new packages shows the same old date - Nov 13th.

As it turns out, the previous time dmaketgz was running, the created docker image was cached and the release date was kept in it as SOURCE_DATE_EPOCH variable. When running it again, docker found a cached image and used it instead of recreating. As a result, I got a new set of packages and release version, but old release date.

I expected the following

Correct date of release in curlver.h

curl/libcurl version

8.11.0

operating system

Red Hat Linux

[andrewkirillov-ibm]

There are few solutions possible:

• Mention in release instructions that a docker rmi <image id> should be used remove old cached image.
• Use --no-cache option when running docker build (which might be safer to avoid user factor errors).