Chapter 1. Producing a native executable

Procedure

1. Open the Getting Started project pom.xml file and verify that it includes the native profile:

   <profiles>
       <profile>
           <id>native</id>
           <properties>
               <quarkus.package.type>native</quarkus.package.type>
           </properties>
       </profile>
   </profiles>

   Copy to Clipboard Toggle word wrap
   Note

   Using Quarkus native profile allows you to run both the native executable and the native image tests.

2. Build a native executable using one of the following methods:

   1. Build a native executable with Docker:

      ./mvnw package -Pnative -Dquarkus.native.container-build=true

      Copy to Clipboard Toggle word wrap

   2. Build a native executable with Podman:

      ./mvnw package -Pnative -Dquarkus.native.container-build=true -Dquarkus.native.container-runtime=podman

      Copy to Clipboard Toggle word wrap

      These commands create the getting-started-*-runner binary in the target directory.

      Important

      Compiling a Quarkus application to a native executable consumes a lot of memory during analysis and optimization. You can limit the amount of memory used during native compilation by setting the quarkus.native.native-image-xmx configuration property. Setting low memory limits might increase the build time. For more details, refer to Native executable configuration properties.

3. Run the native executable:

   ./target/getting-started-*-runner

   Copy to Clipboard Toggle word wrap

   When you build the native executable the prod profile is enabled and the Quarkus native tests run using the prod profile. You can change this using the quarkus.test.native-image-profile property.