Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-1961

JDK11 Docker image incorrectly uses "Debian unstable (sid)"

    Details

    • Similar Issues:

      Description

      The jenkins/jenkins:jdk11 Docker image is running Debian unstable ("sid") instead of Debian stable ("stretch"). Debian unstable is not intended for production use. Debian stable is intended for production use.

      The most surprising is that the openjdk:11-jdk Docker image that is the base of the jenkins/jenkins:jdk11 Docker image is currently Debian stable. It surprises me that the base image is Debian stable while the derived image jenkins/jenkins:jdk11 is Debian unstable.

      I assume some form of caching in the Docker image construction, or some other issue that is causing Debian unstable to be used instead of Debian stable.

      Seeing the Expected Output

      $ docker run --rm -i -t openjdk:11-jdk cat /etc/os-release
      PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
      NAME="Debian GNU/Linux"
      VERSION_ID="9"
      VERSION="9 (stretch)"
      ID=debian
      HOME_URL="https://www.debian.org/"
      SUPPORT_URL="https://www.debian.org/support"
      BUG_REPORT_URL="https://bugs.debian.org/"
      

      Seeing the Unexpected Output

      $ docker run --rm -i -t jenkins/jenkins:jdk11 cat /etc/os-release
      PRETTY_NAME="Debian GNU/Linux buster/sid"
      NAME="Debian GNU/Linux"
      ID=debian
      HOME_URL="https://www.debian.org/"
      SUPPORT_URL="https://www.debian.org/support"
      BUG_REPORT_URL="https://bugs.debian.org/"
      

        Attachments

          Activity

          Hide
          alecharp Adrien Lecharpentier added a comment -

          After discussing with Mark Waite, I dig a bit in this problem, which is clearly one.

          I can see that docker image inspect --format='{{json .RootFS.Layers'}} for both jenkins/jenkins:jdk11 and openjdk:11-jdk have nothing in common. I would have expected that layers from openjdk:11-jdk image would be in jenkins/jenkins:jdk11 image.

          Is is possible that an old version of the openjdk:11-jdk image was already on the system and it needs to be pulled again?

          As Oleg said he will have limited bandwidth, you do think you could take a look at this Baptiste Mathus?

          Show
          alecharp Adrien Lecharpentier added a comment - After discussing with Mark Waite , I dig a bit in this problem, which is clearly one. I can see that docker image inspect --format='{{json .RootFS.Layers '}} for both jenkins/jenkins:jdk11 and openjdk:11-jdk have nothing in common. I would have expected that layers from openjdk:11-jdk image would be in jenkins/jenkins:jdk11 image. Is is possible that an old version of the openjdk:11-jdk image was already on the system and it needs to be pulled again? As Oleg said he will have limited bandwidth, you do think you could take a look at this Baptiste Mathus ?
          Hide
          markewaite Mark Waite added a comment -

          Confirmed that the Docker image jenkins/jenkins:jdk11 now reports the expected output. Thanks Baptiste Mathus for merging that pull request!

          Show
          markewaite Mark Waite added a comment - Confirmed that the Docker image jenkins/jenkins:jdk11 now reports the expected output. Thanks Baptiste Mathus for merging that pull request!

            People

            • Assignee:
              markewaite Mark Waite
              Reporter:
              markewaite Mark Waite
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: