Deployment Manual / The java-application-base Configuration

Deployment Manual / Version 2406.0

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_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>
    </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.
	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.

Search Results

Table Of Contents