docker-maven-plugin VS jib

So there are multiple ways of building Docker images for Java apps. For instance, this is probably one of the oldest plugins for Maven: https://github.com/spotify/docker-maven-plugin.

After digging a bit deeper, I realized something interesting. The project wasn’t using a Dockerfile at all. Instead, it was using Jib.

Inspired by .NET's native container support and tools like Jib (Java) and ko (Go), pycontainer-build provides a Python-native way to create OCI-compliant container images.

We use jib at work (https://github.com/GoogleContainerTools/jib) which also skips the Dockerfile and builds an image for a Java project directly.

This certainly looks like a much nicer experience than docker build, especially given that there can be a cache hit after a cache miss.

Official documentation: https://github.com/GoogleContainerTools/jib

GitHub - GoogleContainerTools/jib: 🏗 Build container images for your Java applications.

Worth to mention the benefits of using Jib Maven Plugin to build our Spring Boot applications images. Jib help us with image build optimization and customization.

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:

JIB

It is pretty easy to do with https://github.com/GoogleContainerTools/jib.