Skip to content

Latest commit

 

History

History
62 lines (44 loc) · 2.09 KB

quarkusjibextension.adoc

File metadata and controls

62 lines (44 loc) · 2.09 KB
Raw

Quarkus Container Extension Jib

Plugin configuration

  <dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-container-image-jib</artifactId>
  </dependency>

By default the plugin send the packaged application to /home/jboss`.

Default image
Figure 1. Default image

The extension parameters are used to change the target folder to /deployments/dependencies but can’t allow to use another source than the dependencies defined in the pom.xml.

The maven command used is k8s:build k8s:push. An example would be :

mvn -e install -Dmaven.repo.local=/tmp/artifacts/m2     --global-settings /tmp/kit-cfkvvqjdm89s73c9irb0-351212210/maven/settings.xml  -Dmaven.artifact.threads=12 -T 12 -Dquarkus.container-image.builder=jib -Dquarkus.container-image.push=true -Dquarkus.container-image.registry=localhost:5000 -Dquarkus.container-image.group=firstimage -Dquarkus.container-image.name=camel-k-integration  -Dquarkus.container-image.tag=latest -Dquarkus.container-image.insecure=true  -Dquarkus.jib.working-directory=/deployments/dependencies -Dquarkus.jib.base-jvm-image=eclipse-temurin:11

Incremental build

❌
 Incremental build is not good enought. Each build add the full target/lib folder content, and it is not possible to change to another folder. This results in a lot of wasted space.
First image
Figure 2. First image
Second image
Figure 3. Second image
Third image
Figure 4. Third image

Multi-architecture

✔️
 Multi-architecture is validated

The Quarkus Container Extension Jib allows to configures platforms of base images to select from a manifest list by adding this command property -Dquarkus.jib.platforms="linux/amd64,linux/arm64/v8".