Update Dockerfile for 1.15.2

[raboof]

I have checked the build succeeds. Running the image produces:

$ docker run sha256:c70ba6627cde737c1cb56e8a858a
    _________________________     __
   / _____/ ______/ ______/ /____/ /
  / /  __/ /___  /_____  / _____  / 
 / /__/ / ____/  _____/ / /    / /  
/______/_/      /______/_/    /_/    1.15.2

Monitor and Manage Apache Geode
gfsh>
Exiting... 
$

That looks OK to my untrained eye.

For all changes:

• Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

• Has your PR been rebased against the latest commit within the target branch (typically develop)?

• Is your initial contribution a single, squashed commit?

• Does gradlew build run cleanly?

• Have you written or updated unit tests to verify your changes?

• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[JinwooHwang]

Hi @raboof, could you help me understand why 1A3694A1448840FC3B1137B2CAE347D5AE2E5C93 was replaced with 62F7DA41B7D8F26C? The new value seems significantly shorter, and I’d like to understand the reasoning or context behind the change.

[raboof]

The reason for the change is that 1.15.1 was signed by http://keyserver.ubuntu.com:11371/pks/lookup?search=1A3694A1448840FC3B1137B2CAE347D5AE2E5C93&fingerprint=on&op=index and 1.15.2 was signed by you, http://keyserver.ubuntu.com:11371/pks/lookup?search=62F7DA41B7D8F26C&fingerprint=on&op=index

I'm not sure where the change in length comes from, I guess it's different formattings of the key IDs.

[JinwooHwang]

Thank you for the clarification, @raboof. I noticed that the key 62F7DA41B7D8F26C isn’t listed in https://github.com/apache/geode/blob/develop/KEYS. @niallkp, is this omission expected, or might I be overlooking something? Your insight would be greatly appreciated.

[raboof]

There was some discussion on the lists about this, https://lists.apache.org/thread/roo6gkgypjnp51g3rtvn4thvmbjl2bfs - I think whether to have the KEYS file in version control as well was also discussed somewhere, but I can't find a reference right now

[raboof]

whether to have the KEYS file in version control as well was also discussed somewhere, but I can't find a reference right now

Ah that was in #7919

[JinwooHwang]

whether to have the KEYS file in version control as well was also discussed somewhere, but I can't find a reference right now

Ah that was in #7919

That's right, @raboof. It seems we haven’t yet heard from @CalvinKirs on that issue.

[JinwooHwang]

Thanks for the clarification, @raboof . As long as 62F7DA41B7D8F26C functions as expected, we're in good shape. We can address its absence from the KEYS file in a separate ticket or PR. Thank you so much for taking care of this issue.

[JinwooHwang]

Hi @raboof . when you have a moment, could you please confirm whether it ran successfully?

[raboof]

I have checked the build succeeds. Running the image produces:

$ docker run sha256:c70ba6627cde737c1cb56e8a858a
    _________________________     __
   / _____/ ______/ ______/ /____/ /
  / /  __/ /___  /_____  / _____  / 
 / /__/ / ____/  _____/ / /    / /  
/______/_/      /______/_/    /_/    1.15.2

Monitor and Manage Apache Geode
gfsh>
Exiting... 
$

^ it starts, but I haven't used it beyond that yet

[JinwooHwang]

Thank you so much, @raboof .