The dockerfile-maven-plugin has been replaced with the google-jib-plugin to build OCI conform container images, because the dockerfile-maven-plugin is no longer maintained.

The google-jib-plugin plugin integrates well with Spring Boot applications and allows to build images securely without Docker being installed. This allows for a rootless, daemonless build but restricts the image building process to use only adding image layers by adding resources. There is no possibility to execute any RUN steps during the build process. Building the images without Docker now requires a configured container registry although it is still possible to build images in the local Docker daemon, without the need of a registry.

The switch to the new image build process is tightly coupled to the recent change to build all artifacts in a reproducible manner, resulting in identical image digests when the source has not changed. With Spring Boot layered applications, this results in a faster build and smaller upload size to your container registry. Because file and image creation date affect the resulting image digest, jib sets the date to Unix epoch (00:00:00, January 1st, 1970 in UTC). If you do not like this, you can enable the current timestamp in the jib-maven-plugin, but this sacrifices reproducibility since the timestamp will change with every build.

 <container>
  <useCurrentTimestamp>true</useCurrentTimestamp>
</container>
 

As a result of this change, the image build process moved to the application modules and the Docker directory hierarchy has been removed.

All Spring Boot application images are still based on the coremedia/java-application-base images will run with only some small breaking changes to the previous images. The breaking changes include:

To build the images, the properties and Maven profiles have changed:

The new images do not contain any health checks directive any more. If you rely on the Docker health checks, please define them either on the command line or in your docker-compose file.

 services:
  foo:
    test: [ "CMD", "curl", "-Lf", "http://localhost:8081/actuator/health" ]
    interval: 30s
    timeout: 10s
    retries: 3
    start_period: 40s
docker run --health-cmd='curl -Lf http://localhost:8081/actuator/health || exit 1' \
    --health-interval=30s \
    --health-timeout=10s \
    --health-start-period=40s \
    --health-retries=3 <image>
 

For the Commerce Adapter the health check looks like this:

 services:
  commerce-adapter-mock:
    test: [ "CMD", "curl", "-Lf", "http://localhost:8081/actuator/health" ]
    interval: 30s
    timeout: 10s
    retries: 3
    start_period: 40s

docker run --health-cmd='curl -Lf http://localhost:8081/actuator/health || exit 1' \
    --health-interval=30s \
    --health-timeout=10s \
    --health-start-period=40s \
    --health-retries=3 <image>