maven-wrapper VS jib

If no idea what maven wrapper is, read this: https://maven.apache.org/wrapper/

You need to build Docker images for each app. This is specific to the JHipster application used in this tutorial which uses Jib to build the images. Make sure you are logged into Docker using docker login. Navigate to each app folder (store, invoice, product) and run the following command:

We are ready to deploy now. First, we need to build and push the images to the registry. We can use the handy Jib commands provided by JHipster. Navigate to each of the microservice folders and run the commands below.

I would avoid Docker all together and use https://github.com/GoogleContainerTools/jib

You might be interested in trying out Jib. I believe it uses eclipse-temurin by default.

% mvn compile jib:build [INFO] Scanning for projects... [INFO] [INFO] ------------------------< net.shagie:hello-jib >------------------------ [INFO] Building Hello Jib 0.0.1-SNAPSHOT [INFO] --------------------------------[ jar ]--------------------------------- [INFO] [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @ hello-jib --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Using 'UTF-8' encoding to copy filtered properties files. [INFO] Copying 1 resource [INFO] Copying 0 resource [INFO] [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ hello-jib --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- jib-maven-plugin:2.8.0:build (default-cli) @ hello-jib --- [WARNING] 'mainClass' configured in 'maven-jar-plugin' is not a valid Java class: ${start-class} [INFO] [INFO] Containerizing application to shagie/hellojib... [WARNING] Base image 'gcr.io/distroless/java17:nonroot' does not use a specific image digest - build may not be reproducible ... credential stuff [INFO] Using base image with digest: sha256:2c29be2a889be27e4905127ae7122d390df08ac170791153b54f086ce7507b59 [INFO] [INFO] Container entrypoint set to [java, -cp, /app/resources:/app/classes:/app/libs/*, net.shagie.hellojib.HelloJibApplication] [INFO] [INFO] Built and pushed image as shagie/hellojib [INFO] [INFO] A new version of Jib (3.2.1) is available (currently using 2.8.0). Update your build configuration to use the latest features and fixes! [INFO] https://github.com/GoogleContainerTools/jib/blob/master/jib-maven-plugin/CHANGELOG.md [INFO] Please see https://github.com/GoogleContainerTools/jib/blob/master/docs/privacy.md for info on disabling this update check. [INFO] [INFO] Executing tasks: [INFO] [==============================] 100.0% complete [INFO] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 01:21 min [INFO] Finished at: 2022-04-26T19:32:05-05:00 [INFO] ------------------------------------------------------------------------

That Dockerfile's isn't that complicated. What is even easier is using Jib: https://github.com/GoogleContainerTools/jib

If you want to go with containerization, you can look into https://github.com/GoogleContainerTools/jib or https://buildpacks.io/ that scaffolds your application and generate cloud-native docker image, which can be deployed on any cloud provider.

Depending on the type of project there are very light weight tools to generate OCI images. Like JIB for java apps and ko for golang apps, there tools are very light weight.