Jib builds fast, reproducible container images for Java applications without using a Docker daemon during image construction. It produces Docker- and OCI-compatible images and separates application dependencies into their own layer, allowing rebuilds to reuse dependencies that change less often. section 11.2
Quarkus integrates Jib through the quarkus-container-image-jib extension, but the Quarkus CLI can also invoke it directly. The CLI supports both Maven and Gradle projects; Maven additionally supports the quarkus:image-build goal. section 11.2 section 11.2.1
Build a Reservation service image
Run quarkus image build jib from the service project. Quarkus creates an image such as <username>/reservation-service:1.0.0-SNAPSHOT. Although Jib builds without a daemon, Docker or Podman is still needed when the image must be registered in a local registry. section 11.2.1 section 11.2
Push the resulting image with quarkus image push. The command targets Docker Hub by default and performs a standard docker push, so authentication and matching local and Docker usernames can enable the default workflow. section 11.2.1
