[GitHub] [pulsar] lhotari commented on issue #20420: [Bug] Unexpected lib version in pulsar-all:3.0.0 image

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

lhotari commented on issue #20420:
URL: https://github.com/apache/pulsar/issues/20420#issuecomment-1567051013

   > I think the root cause is that we use `apachepulsar/pulsar:latest` to build the `pulsar-all` image.
   > 
   > https://github.com/apache/pulsar/blob/ab810f4f59dd7d6c8b5313ceb334873a7d2cde31/docker/pulsar-all/Dockerfile#L29-L31
   > 
   > But at the time of building Pulsar 3.0.0, `apachepulsar/pulsar:latest` was pointing to version 2.11.0(I'm curious why it's not 2.11.1).
   
   @cbornet @RobertIndie 
   I don't think that this is the root cause. In the current build, all docker images should be built locally without pulling `apachepulsar/pulsar:latest` from the remote repository. In that case, there's no chance that versions get mixed regardless of the remote versions.
   
   How did the docker images get built and pushed?
   
   We should be updating the release guide if there are problems (which was very common in the past).
   I'd rather have the release guide in the GitHub wiki since that would lower the barrier to update the docs if there are issues that need to be addressed.
   The current release process is maintained on the website, https://pulsar.apache.org/contribute/release-process/#stage-docker-images . That's fine as long as we continue to maintain it.
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   


-- 
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