Google Jib generated Spring Boot docker images are not starting with Docker 25 version

[eazybytes]

Environment:

• Jib version: 3.4.0
• Build tool: Maven 3.8.6
• OS: Mac (Apple Silicon)

Description of the issue: I updated the docker version to 25.0.2 in my local system. With this new version of Docker, I am not able to start any of my Google Jib generated Spring Boot docker images as containers. I tried with docker images that are generated with <Docker 25 and >=Docker 25. The issue is happening for all type of docker images.

Expected behavior:

Steps to reproduce:

1. Download the code present inside the URL https://github.com/eazybytes/microservices/tree/3.2.0/section4/cards
2. Run the command mvn compile jib:dockerBuild to generate docker image
3. Try starting the container using the command docker run -p 9000:9000 eazybytes/cards:s4

jib-maven-plugin Configuration:

      <plugin>
    <groupId>com.google.cloud.tools</groupId>
    <artifactId>jib-maven-plugin</artifactId>
    <version>3.4.0</version>
    <configuration>
        <to>
        <image>eazybytes/${project.artifactId}:s4</image>
        </to>
       </configuration>
     </plugin>

Log output:

/\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::                (v3.2.0)

2024-02-05T09:22:49.143Z  INFO 1 --- [           main] com.eazybytes.cards.CardsApplication     : Starting CardsApplication using Java 17.0.9 with PID 1 (/app/classes started by root in /)
2024-02-05T09:22:49.157Z  INFO 1 --- [           main] com.eazybytes.cards.CardsApplication     : No active profile set, falling back to 1 default profile: "default"
[Too many errors, abort]
qemu: uncaught target signal 6 (Aborted) - core dumped

[AntoineDuComptoirDesPharmacies]

Hi @eazybytes,

Exactly the same problem at LeComptoirDesPharmacies. Our collaborators update their docker dekstop and we can not run Spring Boot in docker since this update (same error). The workaround on our side is to rollback and use an older version of docker.

Yours faithfully, LCDP

[eazybytes]

Can we please know any ETA to fix this issue ?

[eazybytes]

The issue is resolved after upgrading to the recent version of Docker Desktop which is 4.28.0