Mismatched versions of JDK 11 between che-java11-maven:7.1.0 and che-remote-plugin-runner-java11:7.1.0; also for JDK 8

[nickboldt]

Describe the bug

https://quay.io/repository/eclipse/che-java11-maven?tab=tags

:7.1.0 and :nightly tags are all JDK 11.0.3

$➔ docker run -it  --entrypoint /bin/sh quay.io/eclipse/che-java11-maven:7.1.0 -c "java -version" | head -2

openjdk version "11.0.3" 2019-04-16
OpenJDK Runtime Environment (build 11.0.3+1-Debian-1bpo91)

But in the remote plugin runner:

https://hub.docker.com/r/eclipse/che-remote-plugin-runner-java11/tags?page=1&ordering=last_updated

:7.1.0, :next and :latest tags are all JDK 11.0.4

$➔ docker run -it  --entrypoint /bin/sh docker.io/eclipse/che-remote-plugin-runner-java11:7.1.0 -c "java -version" | head -2
openjdk version "11.0.4" 2019-07-16
OpenJDK Runtime Environment (build 11.0.4+11-alpine-r0)

The result is a mismatch between debugger and debuggee:

Che version

• latest
• nightly
• 7.1.0

Steps to reproduce

1. User ran the command option “Debug”.

2. Select “Open Configurations” under “Debug”

3. Select “Attach”

4. Update port to 8000 where I define in the devfile command JDWP port 8000:

5. Select “Start Debugging” under “debug”

6. It will take a while to attach the JVM

7. Then, the debug console will complain about the mismatching versions.

Expected behavior

Runtime

• kubernetes (include output of kubectl version)
• Openshift (include output of oc version) 3.11
• minikube (include output of minikube version and kubectl version)
• minishift (include output of minishift version and oc version)
• docker-desktop + K8S (include output of docker version and kubectl version)
• other: (please specify)

Screenshots

Installation method

• chectl
• che-operator
• minishift-addon
• I don't know

Environment

• my computer
  • Windows
  • Linux
  • macOS
• Cloud
  • Amazon
  • Azure
  • GCE
  • other (please specify)
• other: please specify

Additional context

[nickboldt]

Aside:

I found the source for https://hub.docker.com/r/eclipse/che-remote-plugin-runner-java11 -> https://github.com/eclipse/che-theia/blob/master/dockerfiles/remote-plugin-java11/Dockerfile

but I can't find the source for https://quay.io/repository/eclipse/che-java11-maven ... where is it?

See #14623 for followup since no one replied here.

[rhopp]

Not sure who should take a look at this one. Maybe your team, @skabashnyuk?

[nickboldt]

User also tried to enable debugger using che-java8-maven:7.1.0 and che-remote-plugin-runner-java8:7.1.0 and got a similar mismatch result:

Alpine 3.9.4 image

$➔ docker run -it  --entrypoint /bin/sh docker.io/eclipse/che-remote-plugin-runner-java8:7.1.0 -c "java -version && grep PRETTY /etc/os-release"

openjdk version "1.8.0_212"
OpenJDK Runtime Environment (IcedTea 3.12.0) (Alpine 8.212.04-r1)
OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)
PRETTY_NAME="Alpine Linux v3.9"

vs.

$➔ docker run -it  --entrypoint /bin/sh quay.io/eclipse/che-java8-maven:7.1.0 -c "java -version && grep PRETTY /etc/os-release"

openjdk version "1.8.0_222"
OpenJDK Runtime Environment (build 1.8.0_222-b10)
OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode)
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"

If both images were based on UBI8, we could avoid these problems. See #14113 and https://issues.jboss.org/browse/CRW-354

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.