Broken (community) image due to today's release of CentOS 7.6 #206
Comments
|
Yup, it would seem to me that despite using the completely fixed versions (which is defined here) using the Base Container FROM "centos:7.5.1804" and RPM yum install "java-1.8.0-openjdk-1.8.0.181-3.b13.el7_5", the release of the new CentOS 7.6 container image just broke the old one 7.5.1804, check this out, which worked before: What's curious is that |
|
Also seen here https://circleci.com/gh/fabric8io-images/s2i/498 following merge of #205 - not caused by it. |
|
Looks like the parent directory is missing |
sure but how did it suddenly disappear given a fixed version of base image and OpenJDK? This is really weird, the CentOS (7.5.1804) image hasn't changed in 4 months even locally: I'm going to look more at the OpenJDK (RPM) installation side of things... |
|
Commenting out that Did I just completely break this with #205 ? I had tested it, and |
Looks like it.. does the exact position of the |
vorburger
changed the title
|
Ignore earlier comments above re. CentOS, this was a misinterpretation; it's got absolutely nothing to do with that, but it's the |
|
It still failed on https://circleci.com/gh/fabric8io-images/s2i/500, and now that I'm looking more closely I am seeing what already on https://circleci.com/gh/fabric8io-images/s2i/498 4 hours ago but I initially missed: |
|
It likely had nothing at all to do with #115, so reverting a9bd456 in c23d43f. 80d07d6 ensures future non-regression and helps to sure that we get a much clearer error now: The observed very confusing behaviour which lead me down a wrong interpretation re. Now we're back to square one, and I do suspect something is really wrong, in Docker itself, or on Docker Hub, or with the CentOS image update, because how on earth is this possible: How can the (old) Something is really off here. |
|
Just to make sure this isn't some local screw-up, even though it clearly does happen on Circle CI as well, I've just done a |
|
It's BECAUSE you are using fixed versions that you have the error. Don't. Install just the package name and you get the latest. |
|
b57b0df ditches Java 8 package minor version number which fixes this; https://circleci.com/gh/fabric8io-images/s2i/504 passed again. 8bad895 does the same for the #172 has something somewhat related to this problem; basically this project may have misunderstood CentOS versions - for both packages and the images themselves: Full transcript of what I learnt today in this regard preserved on https://gist.github.com/vorburger/ea367a76f69aafb8260c62f6bedf2788, but the gist of it is basically that there is |
vorburger
changed the title
Unless I'm stupid, I think the new CentOS just released to Docker Hub, hours ago, broke
./test.shfor the existing Java 8 image (forget about Java 11 for #193) ... this seems weird, and worth investigating and possibly escalating to the CentOS community, if confirmed.The text was updated successfully, but these errors were encountered: