JibProcessor hangs with native image build for Quarkus 3.20.0

[erik-wramner]

I'm trying to upgrade from 3.15.4 LTS to 3.20.0 LTS. The build works, but in the final step when it creates a docker image, it just hangs. No CPU usage, nothing happens.

This is on Windows. The output until it hangs:

[INFO] [io.quarkus.deployment.pkg.steps.NativeImageBuildRunner] docker run --env LANG=C --rm -v /PATH/app-native-image-source-jar:/project:z --entrypoint /bin/bash quay.io/quarkus/ubi9-quarkus-mandrel-builder-image:jdk-21 -c objcopy --strip-debug app-runner
[INFO] [io.quarkus.container.image.jib.deployment.JibProcessor] Starting (local) container image build for native binary using jib.
[INFO] [io.quarkus.container.image.jib.deployment.JibProcessor] Using docker to run the native image builder
[WARNING] [io.quarkus.container.image.jib.deployment.JibProcessor] Base image 'quay.io/quarkus/ubi9-quarkus-micro-image:2.0' does not use a specific image digest - build may not be reproducible
[INFO] [io.quarkus.container.image.jib.deployment.JibProcessor] Using base image with digest: sha256:a27b0bb76e972be9189fa3583548313b81c4c130d9c763c21b34583b60160153
[INFO] [io.quarkus.container.image.jib.deployment.JibProcessor] Container entrypoint set to [./application]```

Running the docker command manually has the same effect. This works well with 3.15.4. What has changed? Anyone else with the same problem?

EDIT: experimenting a bit, if I change the volume mount to use the target folder rather than the source jar folder, this step works. The problem is that the app-runner file does not exist in the source jar folder. However, the mount is generated, so the question becomes how to fix it (or fix so that the runner file gets copied into the right place).

[quarkus-bot[bot]]

/cc @geoand (jib)

[geoand]

cc @zakkak

[zakkak]

@erik-wramner can you please share a reproducer?

[erik-wramner]

Please see https://github.com/erik-wramner/native-build-with-jib-hangs-reproducer.

There are two tags, one for each Quarkus version. For me on Windows 11 with Docker Desktop, running build-reproducer.cmd hangs on 3.20 and works fine on 3.15. The project structure follows the one we have for real, but greatly simplified. There are almost no dependencies left and no real code.

I've tested with other releases and 3.16.4 fails, so everything after 3.15 fails while 3.15 works.

[erik-wramner]

I found a workaround. This works:

<properties>
    <quarkus.native.enabled>true</quarkus.native.enabled>
    <quarkus.native.remote-container-build>true</quarkus.native.remote-container-build>
    <quarkus.remote-container-image.build>true</quarkus.remote-container-image.build>
</properties>

I.e., using remote container build instead of local. As the wrong folder is mounted, that makes sense. It would still be nice to get this fixed, but at least now we can continue with the upgrade.

[erik-wramner]

Actually @geoand it didn't work. The build succeeds, but there is no new docker image. Trying to find the right options...

[erik-wramner]

After a lot of trial and error, back at square one. It seems the build works on Windows 10... but I still can't get it through on my main computer with Windows 11, even though the 3.15.4 build still works just fine. With remote, it can copy the correct files to a volume rather than map the directory, but it still hangs on the same line setting the entry point.

[erik-wramner]

We are giving up on this one. We will use the docker plugin instead, that works. A pity.