Re: [I] [Doc] Docker image build instructions update [pulsar]

["yohimik (via GitHub)" <gi...@apache.org>]

yohimik commented on issue #21071:
URL: https://github.com/apache/pulsar/issues/21071#issuecomment-5610280426

   A version-specific update for anyone finding this issue: current `master` now uses Gradle. [`docker/build.sh`](https://github.com/apache/pulsar/blob/5a47023fa3b29a432649352c0d056a4d3f847203/docker/build.sh) invokes `./gradlew :docker:pulsar-docker-image:dockerBuild`, and the [current Docker README](https://github.com/apache/pulsar/blob/5a47023fa3b29a432649352c0d056a4d3f847203/docker/README.md) describes that route after building the project. The Maven command discussed above needs to stay tied to the older branch it targets.
   
   For the historical multi-arch instructions, #20420 is a useful regression case: `pulsar-all:3.0.0` contained 2.11.0, and maintainers resolved it with 3.0.1. The [3.0.0 child Dockerfile](https://github.com/apache/pulsar/blob/v3.0.0/docker/pulsar-all/Dockerfile) used `FROM apachepulsar/pulsar:latest`. A build guide should verify both the intended parent reference and the version inside each final architecture, rather than only the child tag.
   
   I checked Docker Hub's manifests on 10 September 2026: both `apachepulsar/pulsar-all:3.0.0` and `:3.0.1` still resolve with amd64/arm64 entries. The latter index is `sha256:40835166baed562973fceeb108fc8e43adbbcb2fe8e23e84052ff39ac35ab9d2`. This was a manifest-only check, not a fresh execution of those old images; the content mismatch and repair are the maintainer-confirmed history above.
   
   Disclosure: I maintain [dispat](https://github.com/yohimik/dispat). Its [Docker graph example](https://dispat.dev/examples/docker/) models the provider-publication-before-consumer-build boundary, but that ordering still requires an exact provider tag/digest. The smaller useful change here is to document and test that invariant in the branch-specific build instructions.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org