Deployment Manual / The java-application-base Configuration

Deployment Manual / Version 2304

Table Of Contents

The java-application-base Configuration

<configuration>
  <container>
    <entrypoint>INHERIT</entrypoint> 
    <args>
      <arg>application</arg> 
    </args>
    <user>coremedia:coremedia</user> 
    <environment> 
      <JAVA_HEAP>256m</JAVA_HEAP>
      <JAVA_PARALLEL_GC>true</JAVA_PARALLEL_GC>
      <SPRING_BOOT_EXPLODED_APP>true</SPRING_BOOT_EXPLODED_APP> 
      <SPRING_BOOT_EXPLODED_MAINCLASS>@jib-main-class-file</SPRING_BOOT_EXPLODED_MAINCLASS> 
      <SPRING_BOOT_EXPLODED_CLASSPATH>@jib-classpath-file</SPRING_BOOT_EXPLODED_CLASSPATH> 
    </environment>
    <ports>
      <port>8080</port>
      <port>8081</port>
      <port>8199</port> 
    </ports>
  </container>
</configuration>

	With this directive, we tell Jib to inherit the entrypoint information from the base image. In this case it is `/coremedia/entrypoint.sh`.
	The argument to the entrypoint script. The `application` script encapsulates the startup logic. Visit the DockerHub page of the coremedia/java-application-base image for more details.
	The user to start the application. With this base image, we need to use the `coremedia` user to start the application.
	The environment variables the `application` entrypoint chain script can be configured.
	With this environment variable we tell the script to extract or expect an extracted spring boot app in the image. Jib always extracts the application, because of the Spring-Boot layered jar approach.
	The application starter class we defined in the properties section above.
	The classloader classpath. This mimics the classloading, the Spring-Boot Jib extension automatically sets.
	With the java-application-base image, we can activate the jmx-prometheus-agent. With the distroless approach either using the prometheus actuator is the preferred way.

Search Results

Table Of Contents