Jib

What Jib is

Jib builds Docker and OCI images for Java applications without a Docker daemon. Java teams can use it as a Maven or Gradle plugin, Java library, or command-line interface. It separates application contents into layers, allowing code changes to be rebuilt without rebuilding the entire image. Jib can push images to a container registry of the user's choice, uses an OpenJDK base image by default, and allows a custom base image. The project says that rebuilding an image with the same contents generates the same image. It lists local build-cache backends and multi-architecture builds, and says Jib works well with Google Cloud Build. Repository examples cover Spring Boot, Micronaut, multi-module projects, and Spark Java with a Java Agent. Jib is free and open source under Apache License, Version 2.0. The project is not an officially supported Google product; it directs usage questions to Stack Overflow and also links to GitHub issues and a FAQ. It is listed for Linux, macOS, and Windows.

Who it suits

Jib is for people building container images for Java applications, including users of Maven, Gradle, Java libraries, or command-line workflows. Its daemonless build method may suit teams that want to build without a Docker daemon.

Limits

The listed build-cache backend is local.

Getting started

1. Open the Jib project on GitHub
2. Choose the Maven or Gradle plugin, Java library, or command-line interface
3. Use the default OpenJDK base image or configure a custom base image
4. Build the image and push it to a container registry of your choice

Verdict

Jib offers Java-focused image building through several interfaces, with layered builds and registry support. Keep in mind that Google does not officially support the project.