FYI official-images PR is now submitted: https://github.com/docker-library/official-images/pull/11000
Thanks for your help Hoss! ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Thu, Sep 30, 2021 at 1:32 PM Chris Hostetter <hossman_luc...@fucit.org> wrote: > > David: I submitte a PR to docker-solr to hardocde the archs for 6.* and > 5.* releases in generate-stackbrew-library.sh > > https://github.com/docker-solr/docker-solr/pull/388 > > I'll let you RTC and deal with the final docker-library/official-images PR > since I have no established credibility with docker-library to broach the > "our GitCommit for 8.9 doesn't exist, why is your tooling not freaking out > about this and how is the 8.9 version being built as a result?" portion of > the discussion. :) > > > > : Date: Thu, 30 Sep 2021 00:10:50 -0400 > : From: David Smiley <dsmi...@apache.org> > : Reply-To: dev@solr.apache.org > : To: dev@solr.apache.org > : Subject: Re: 8.10 docker image please > : > : I dug into this some. The 8.9 commit hash there (a1a59) was incorrect; > it > : was for a PR that after merging became something else. > : https://github.com/docker-solr/docker-solr/pull/380 (see first commit in > : there). > : The official-docker-images PR was crafted prematurely by the contributor. > : I'm not sure what consequence this has but it ought to be pointed out in > : our 8.10 PR to official-images. > : > : Regarding the arm64v8 tags, those should be removed manually, or fix the > : root cause that probably lies in that generate-stackbrew-library.sh > : script. See the PR comments about that here: > : https://github.com/docker-library/official-images/pull/10403 > : > : I can do these things tomorrow at some point. > : > : ~ David Smiley > : Apache Lucene/Solr Search Developer > : http://www.linkedin.com/in/davidwsmiley > : > : > : On Wed, Sep 29, 2021 at 10:03 PM Chris Hostetter <hoss...@fucit.org> > wrote: > : > : > > : > : 2) changing the GitCommit associated with 8.9.0 > : > : > : > : ...the last one is the biggest WTF, allthough frankly the 'new' > : > GitCommit > : > : seems "correct" while the 'old' GitCommit (currently listed in > : > : docker-library/official-images.git's copy of library/solr) doesn't > exist > : > : at all in docker-solr/docker-solr.git AFAICT -- which defeats the > point > : > of > : > : this GitCommit in the manifest file as i understand it -- so i really > : > have > : > : no idea WTF is going on, or if any of this is "correct" ... > : > > : > Hmmm.... > : > > : > (Manually crafted URL to see what github thinks about it) > : > > : > > https://github.com/docker-solr/docker-solr/commit/a1a59aa9d3ef286fe1e046ddfd168c3c34720660 > : > > : > "This commit does not belong to any branch on this repository, and may > : > belong to a fork outside of the repository." > : > > : > > : > ...so how/why does the current library/solr file in > : > docker-library/official-images.git "work" in it's current state? does > : > docker-library really just not care at all about the GitCommit when > : > generating official images? > : > > : > > : > > : > -Hoss > : > > : > --------------------------------------------------------------------- > : > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org > : > For additional commands, e-mail: dev-h...@solr.apache.org > : > > : > > : > > -Hoss > http://www.lucidworks.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org > For additional commands, e-mail: dev-h...@solr.apache.org > >
