vorburger
commented
5 years ago 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:
Step 7/37 : RUN yum install -y unzip java-1.8.0-openjdk-1.8.0.181-3.b13.el7_5 java-1.8.0-openjdk-devel-1.8.0.181-3.b13.el7_5 && curl https://archive.apache.org/dist/maven/maven-3/3.5.4/binaries/apache-maven-3.5.4-bin.tar.gz | tar -xzf - -C /opt && ln -s /opt/apache-maven-3.5.4 /opt/maven && ln -s /opt/maven/bin/mvn /usr/bin/mvn && groupadd -r jboss -g 1000 && useradd -u 1000 -r -g jboss -m -d /opt/jboss -s /sbin/nologin -c "JBoss user" jboss && chmod 755 /opt/jboss
---> Using cache
---> 093f954f1101
Step 8/37 : ENV JAVA_HOME /etc/alternatives/jre
---> Using cache
---> 4720429c8d1d
Step 9/37 : RUN echo securerandom.source=file:/dev/urandom >> /usr/lib/jvm/java/jre/lib/security/java.security && usermod -g root -G jboss jboss
---> Running in fc3c875102bb
/bin/sh: /usr/lib/jvm/java/jre/lib/security/java.security: No such file or directory
The command '/bin/sh -c echo securerandom.source=file:/dev/urandom >> /usr/lib/jvm/java/jre/lib/security/java.security && usermod -g root -G jboss jboss' returned a non-zero code: 1What's curious is that centos:7.5.1804 on https://hub.docker.com/r/library/centos/tags/ says "2 months ago" ... unless I'm not getting it from there? This is weird... @ctron @rhuss please jump in and shout if you get what' going on here...
ctron
TrevorPH
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.