Custom base image ignored with Jib Gradle 1.6.0

[lpellegr]

Environment:

• Jib version: 1.6.0
• Build tool: Gradle 5.6.1
• OS: Fedora 30

Description of the issue:

I have a Gradle app that is configured to use Java 12:

sourceCompatibility = 12
targetCompatibility = 12

It is packaged with Jib. Since Jib includes support for Java 11 only by default, I specify a Java 12 base image as follows. Unfortunately, when I run gradle jibDockerBuild, the task fails with the following message:

Your project is using Java 12 but the base image is for Java 11, perhaps you should configure a Java 12-compatible base image using the 'jib.from.image' parameter, or set targetCompatibility = 11 or below in your build configuration

Expected behavior:

Gradle jibDockerBuild task completes with success.

Steps to reproduce:

1. Create a basic Java 12 app using Gradle.
2. Include Gradle Jib definition as follows.
3. Run gradle jibDockerBuild.

jib-gradle-plugin Configuration:

jib {
    container {
        jvmFlags = [
                '-server',
                '-Xms6g',
                '-Xmx6g',
                '-XX:+UnlockExperimentalVMOptions',
                '-XX:+UseShenandoahGC',
                '-Dauto-update.temp.dir=/root',
                '-Dmanagement.endpoints.jmx.exposure.exclude=*',
                '-Dmanagement.endpoints.web.exposure.include=health',
                '-Dspring.application.admin.enabled=false',
                '-Dspring.jmx.enabled=false'
        ]
        mainClass 'com.acme.Application'
    }
    from {
        image 'adoptopenjdk/openjdk12:slim'
    }
    to {
        auth {
            image = 'registry.hub.docker.com/acme/api:latest'
            username = 'acme'
            password = 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
        }
        tags = ['latest']
    }
}

Additional Information: Downgrading to Jib Gradle version 1.5.1 solves the issue. It seems a change was introduced with version 1.6.0. I tried adding the prefix 'registry://' to the base image name but the task still fails.

[chanseokoh]

@lpellegr thanks for reporting the bug. The version check is broken rather than the base image is ignored. We will fix this soon.

Just so you know, 1.5.0 and 1.5.1 suffer from an issue of substantially slower network performance than 1.6.0 and 1.4.0.

     String baseImageConfig =
-        rawConfiguration.getFromImage().orElse(getDefaultBaseImage(projectProperties));
+        rawConfiguration.getFromImage().isPresent()
+            ? rawConfiguration.getFromImage().get()
+            : getDefaultBaseImage(projectProperties);
     if (baseImageConfig.startsWith(Jib.TAR_IMAGE_PREFIX)) {
       return JavaContainerBuilder.from(baseImageConfig);
     }

[TadCordle]

@lpellegr We just released v1.6.1 with the fix.

[lpellegr]

Great, thanks!