jib: Jib 3.4.2 build fails

Environment:

  • Jib version: 3.4.2
  • Build tool: Gradle 8.7
  • OS: macos

When I run

./gradlew jibDockerBuild

It fails with

Caused by: java.lang.NoSuchMethodError: 'void org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.putArchiveEntry(org.apache.commons.compress.archivers.tar.TarArchiveEntry)'
        at com.google.cloud.tools.jib.tar.TarStreamBuilder.writeAsTarArchiveTo(TarStreamBuilder.java:52)
        at com.google.cloud.tools.jib.image.ImageTarball.dockerWriteTo(ImageTarball.java:166)
        at com.google.cloud.tools.jib.image.ImageTarball.writeTo(ImageTarball.java:84)
        at com.google.cloud.tools.jib.docker.CliDockerClient.load(CliDockerClient.java:195)


Workaround. It works when I set this in both root and gradle submodule build.gradle.kts

buildscript {
    dependencies {
        classpath("commons-codec:commons-codec:1.16.1")
    }
    configurations.all {
        resolutionStrategy {
            force("org.apache.commons:commons-compress:1.26.0")
            force("commons-codec:commons-codec:1.16.1")
        }
    }
}

Please make it work w/o workarounds

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 4
  • Comments: 23 (8 by maintainers)

Most upvoted comments

Other transitive dependencies request 1.21 but Gradle resolves the conflict with the newer version requested by jib-gradle-plugin.

For comparison, we also have the spring-boot-gradle plugin but in our project. It requests 1.21 but gradle resolves it to 1.26.0 in our project:

If your project is a multi-module one, then it’s pretty common that ./gradlew buildEnvironment lies about how it resolved build environment dependencies; it’s a long-standing Gradle bug where build dependencies declared in the parent project shamelessly and silently overrides dependencies of sub-projects, as opposed to what you see from ./gradlew buildEnv.

So, if you haven’t done so, I recommend first that you strictly follow these instructions for setting up your multi-module project. That is, declare all your plugins in the project root while not applying them and then selective apply plugins in sub-projects.


UPDATE: another case of Gradle lying with ./gradlew buildEnv was https://github.com/GoogleContainerTools/jib/issues/4235#issuecomment-2066685245 where an old version of the Apache library was silently pulled in from buildSrc/build.gradle.

Moving the jib plugin version definition to the root of my multi-module project with apply false and using it at the subproject solved the issue for me as well.

I had some free time to look into why my build fails and in my case buildEnvironment wasn’t telling me the truth, because it did not include the dependencies from buildSrc (I have a custom plugin for jOOQ that spins up a testcontainer, to build the DB and generate the DSL).

demo/buildSrc$ ../gradlew -q dependencies

Revealed this:

\--- org.testcontainers:postgresql -> 1.19.7
     \--- org.testcontainers:jdbc:1.19.7
          \--- org.testcontainers:database-commons:1.19.7
               \--- org.testcontainers:testcontainers:1.19.7
                    +--- junit:junit:4.13.2
                    |    \--- org.hamcrest:hamcrest-core:1.3 -> 2.2
                    |         \--- org.hamcrest:hamcrest:2.2
                    +--- org.slf4j:slf4j-api:1.7.36 -> 2.0.12
                    +--- org.apache.commons:commons-compress:1.24.0

While running ./gradlew buildEnvironment was telling me that nothing uses commons-compress except jib and it is on version 1.26.0 which wasn’t the case.

And in this particular case testcontainers already tracks the update, so it’s just a matter of time until the order is restored again… https://github.com/testcontainers/testcontainers-java/issues/8338

The fix was also simple once I figured out what was the problem, I’ve added the following into my buildSrc/build.gradle where I had testcontainers defined:

// buildSrc/build.gradle
dependencies {
  // other plugin deps
  implementation 'org.testcontainers:postgresql:1.19.7'
  implementation 'org.apache.commons:commons-compress:1.26.1'
}

And now both, testcontainers and jib, seem to be working for me.

@mihalyr-prospect there you go! As you saw, the cause is that Gradle pulls in an old version of some library in your build environment for one reason or another where ./gradlew buildEnv lies, which is a known Gradle issue. All you have to do is to resolve your diamond dependency conflict in your project in one way or another. Glad you were able to fix it.

you can take any base spring boot project on 3.2.4

@chanseokoh Aligning the versions in de root project plugins block fixes the problem in our multi-module project. Good to know about this obscure Gradle issue/bug, thanks!

Here is a non multi-module project buildEnvironment (also spring-boot but not using the spring-boot gradle plugin), our compress comes from Jib and it also broke our jibBuildTar step after 3.4.2

+--- com.google.cloud.tools.jib:com.google.cloud.tools.jib.gradle.plugin:3.4.2
|    \--- com.google.cloud.tools:jib-gradle-plugin:3.4.2
|         +--- org.apache.commons:commons-compress:1.26.0

This is on Gradle (wrapper) 8.6, Java 21, and Linux (Fedora 38, but also failing in GitHub CI on ubuntu-latest).

It seems to be the same issue as reported above:

> Task :jibBuildTar FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':jibBuildTar'.
> com.google.cloud.tools.jib.plugins.common.BuildStepsExecutionException: 'void org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.putArchiveEntry(org.apache.commons.compress.archivers.tar.TarArchiveEntry)'

Stacktrace:

Caused by: java.lang.NoSuchMethodError: 'void org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.putArchiveEntry(org.apache.commons.compress.archivers.tar.TarArchiveEntry)'
        at com.google.cloud.tools.jib.tar.TarStreamBuilder.writeAsTarArchiveTo(TarStreamBuilder.java:52)
        at com.google.cloud.tools.jib.hash.Digests.computeDigest(Digests.java:104)
        at com.google.cloud.tools.jib.blob.WritableContentsBlob.writeTo(WritableContentsBlob.java:37)
        at com.google.cloud.tools.jib.cache.CacheStorageWriter.writeUncompressedLayerBlobToDirectory(CacheStorageWriter.java:430)
        at com.google.cloud.tools.jib.cache.CacheStorageWriter.writeUncompressed(CacheStorageWriter.java:282)
        at com.google.cloud.tools.jib.cache.Cache.writeUncompressedLayer(Cache.java:145)
        at com.google.cloud.tools.jib.builder.steps.BuildAndCacheApplicationLayerStep.call(BuildAndCacheApplicationLayerStep.java:108)
        at com.google.cloud.tools.jib.builder.steps.BuildAndCacheApplicationLayerStep.call(BuildAndCacheApplicationLayerStep.java:38)
        at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:131)
        at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:75)
        at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:82)