janhoy commented on PR #23: URL: https://github.com/apache/solr-docker/pull/23#issuecomment-2146299104
The history here is that right after the 9.6 release I upgraded a cluster on my M1 Mac to the new version, but got some strange errors, Solr would not start, but threw some weird low-level JDK IO exception. I spend quite some time before realizing that due to some serious delays before Docker builders built the arm64 images, Docker on my M1 mac decided to insteal pull the armv7 32-bit images that fail due to 64/32 bit mismatch. Worse, even after the arm64 images became available, Docker would NOT pull those automatically until I deleted the faulty image or force-pulled the new. I can imagine that the same would happen on some ARM based cloud server if it happened to auto upgrade immediately after a release announcement, but before the arm64 image was built (this can take 12+ hours). I was not aware we even build a 32 bit image. And I cannot imagine what system would run Solr on such a chip. Some old RasPI perhaps, although nowdays even smaller systems are 64 bit, no? Remember that Docker binary images is a convenience release and the supported architectures are clearly labeled on HUB, so we havent taken anything way or broken any promise, other than perhaps it is surprising to potential 32-bit users that support disappears in a minor release. Also, users can build whatever support they like using the Dockerfile we publish. Do you think we should do an ANNOUNCE type email about this? -- 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: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
