jib-maven-plugin failing with 'No Compressor found for the stream signature' error over some docker images

[leungwh]

Environment:

• jib-maven-plugin 3.4.3
• Maven
• Linux

Description of the issue:
jib-maven-plugin is failing with 'No Compressor found for the stream signature' error over some docker images.

Docker images that failed on jib-maven-plugin with 'No Compressor found for the stream signature' error works fine over standard docker image build commands. So we can assure that those images are not corrupted.

The error only happens on some docker images but not others. So far we cannot find out what specific docker image attribute or content would trigger this error.

Expected behavior:
Build succeeds.

Steps to reproduce:

1. maven execution over pom.xml file (jib-maven-plugin config included)

jib-maven-plugin Configuration:

            <plugin>
                <groupId>com.google.cloud.tools</groupId>
                <artifactId>jib-maven-plugin</artifactId>
                <version>3.4.3</version>
                <configuration>
                    <from>
                        <image>(image path redacted):latest</image>
                    </from>
                    <container>
                        <extraClasspath>/app/resources/logback</extraClasspath>
                        <workingDirectory>/appvol/application</workingDirectory>
                        <entrypoint>
                            <arg>/bin/sh</arg>
                            <arg>-c</arg>
                            <arg>exec java $JAVA_OPTS -javaagent:/app/libs/dd-java-agent-0.103.0.jar -Ddd.trace.sample.rate=1.0 -Ddd.jdbc.analytics.enabled=true -Ddd.logs.injection=true -Dspring.profiles.active=$SPRING_PROFILES_ACTIVE -cp $( cat /app/jib-classpath-file ) $( cat /app/jib-main-class-file )</arg>
                        </entrypoint>
                        <ports>
                            <port>8080</port>
                        </ports>
                    </container>
                </configuration>
            </plugin>

Log output:
[ERROR] Failed to execute goal com.google.cloud.tools:jib-maven-plugin:3.4.3:dockerBuild (default-cli) on project (project name redacted): org.apache.commons.compress.compressors.CompressorException: No Compressor found for the stream signature. -> [Help 1]

[zihenzzz]

i want to fix it.

[diegomarquezp]

Hi @leungwh, thanks for reporting this issue.

This situation is similar to https://github.com/GoogleContainerTools/jib/issues/4382 (but may not count as duplicate).

Would you mind sharing more details about your project structure (even better, a reproducer project)? Also, is this maven configuration the absolute minimal needed to cause this?
Thanks!

[leungwh]

Hi @leungwh, thanks for reporting this issue.

This situation is similar to https://github.com/GoogleContainerTools/jib/issues/4382 (but may not count as duplicate).

Would you mind sharing more details about your project structure (even better, a reproducer project)? Also, is this maven configuration the absolute minimal needed to cause this? Thanks!

Unfortunately, I'm not the actual developer who has encountered this issue. I was reporting this case for my customer.
I'm the provider of the Docker image that triggered the issue. Not the develop who has encountered this issue.
Let me try to inform my customer to contribute on this ticket. To provide the information that you need.

[humphrej]

Hello! I also have seen this problem - some information from my context:

• I have an image built from a Dockerfile "docker build"
• The images gets pushed to a repository using (I think) skopeo
  $ command copy --format v2s2 --dest-creds=$USER:$PASSWORD docker-daemon:$IMAGE docker://$IMAGE
• If I then use that image to build an image using jib I get the "No Compressor found" exception
• If I push the image to a repository using "docker push" then jib has no issues.

The reason I say skopeo (I think) is that the command is wrapped in another and I haven't found the source yet (!) but it looks like a good fit from patten matching the arguments.

[humphrej]

As an update to the above, the "docker push" also had issues with some images. I updated the container push command to skopeo copy to a local directory first as suggested by this comment [1]: docker-daemon -> folder -> container registry. This seems to work better (for now!)

[1] containers/container-libs#246 (comment)