Spring Boot: Run and Build in Docker

It exists many “Docker for Java developers” guides, but most of them does not take care of small and efficient Docker images.

I have combined many resources how to make a simple and fast Docker image containing any of Spring Boot like application.

My goals:

  • Create a single and portable Dockerfile (as general as possible).
  • Make Maven build inside Docker (no need to have Maven locally).
  • Don’t download any Maven dependencies repeatedly, if no changes in pom.xml (rebuilding image as fast as possible).
  • The final Docker image should contain only application itself (no source codes, no Maven dependencies required by Maven build etc.)
  • The final image should be as small as possible (no full JDK required).
  • The application inside Docker should remain configurable as much as possible (with all Spring Boot configuration options).
  • Possibility to enable debug (on demand).
  • Possibility to see log files.

The final image is designed for development purpose, but it does not contain any no-go production parts and it is fully configurable.

To see a working example, see my Github project.

To fulfill a single portable Dockerfile requirement, I need to use Docker multi-stage builds.

It will have two main parts (stages):

  • The building part
  • The runtime part

The building part of the Dockerfile

### BUILD image
FROM maven:3-jdk-11 as builder
# create app folder for sources
RUN mkdir -p /build
WORKDIR /build
COPY pom.xml /build
#Download all required dependencies into one layer
RUN mvn -B dependency:resolve dependency:resolve-plugins
#Copy source code
COPY src /build/src
# Build application
RUN mvn package

I have started from the official Maven image, so you may change this as you wish. The most interesting part is this:

RUN mvn -B dependency:resolve dependency:resolve-plugins

It downloads all dependencies required either by your application or by plugins called during a build process. Then all dependencies are a part of one layer. That layer does not change until any changes in pom.xml found. 

So the rebuilding is very fast and does not include downloading all dependencies again and again.

The second option how to download required dependencies comes from the official Docker Maven site (when you have some problems with the previous variant):

RUN mvn -B -e -C -T 1C org.apache.maven.plugins:maven-dependency-plugin:3.0.2:go-offline

How to customize Maven settings?

It may exist many situations, where you need to change a default Maven setting for your customized build. To do that you need to copy your settings.xml into the image before at the start of the builder image definition, for example:

FROM maven:3-jdk-11 as builder
#Copy Custom Maven settings
COPY settings.xml /root/.m2/

The runtime part of the Dockerfile

FROM openjdk:11-slim as runtime
#Set app home folder
#Possibility to set JVM options (https://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html)

#Create base app folder
#Create folder to save configuration files
RUN mkdir $APP_HOME/config
#Create folder with application logs
RUN mkdir $APP_HOME/log


#Copy executable jar file from the builder image
COPY --from=builder /build/target/*.jar app.jar

ENTRYPOINT [ "sh", "-c", "java $JAVA_OPTS -Djava.security.egd=file:/dev/./urandom -jar app.jar" ]
#Second option using shell form:
#ENTRYPOINT exec java $JAVA_OPTS -jar app.jar $0 $@

The runtime part starts with some necessary step, i.e. exposing port, setting environments and creating some useful folders. The most interesting part is related to copying a previously created jar file into our new image:

#Copy executable jar file from the builder image
COPY --from=builder /build/target/*.jar app.jar

I am copying from the builder image, see the param –from. For more info about copying files from other images, see the Docker documentation page for multi-stage builds.

As for the Spring Boot application, the created jar file is executable, so it is possible to run our application with the single command:

ENTRYPOINT [ "sh", "-c", "java $JAVA_OPTS -Djava.security.egd=file:/dev/./urandom -jar app.jar" ]

To reduce Tomcat startup time there is a system property pointing to “/dev/urandom“.

It exists other options how to run Spring Boot application inside Docker. For more info, visit the official Spring guide.

How to build and run Spring Boot application in Docker in one step?

docker build -t <image_tag> . &amp;&amp; docker run -p 8080:8080 <image_tag>

The above command will build your application with Maven and start it without any delay. This is the simplest way without any customizations. The life may come with some specific requirements, so here’s a couple of them.

Now you can visit the URL to get response from my GitHub example:


How to debug? 

My example uses Java 11, so there are some JVM options to enable debug mode:

docker build -t <image_tag> . &amp;&amp; docker run -p 8080:8080 -p 5005:5005 --env JAVA_OPTS=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005 <image_tag>

You need to add the docker environment variable JAVA_OPTS with JVM options and map the internal debugging port to the outside of the container: -p 5005:5005.

For Java 5-8 containers, use this JAVA_OPTS parameter:


How to setup logging?

The runtime container contains folder /app/log with all log files. This path could be easily mounted into your host:

docker build -t <image_tag> . &amp;&amp; docker run -p 8080:8080 -v /opt/spring-boot/test/log:/app/log <image_tag>

How to change application configuration?

The jar file contains default configuration. To selectively override those values, you have many options. I will show you some a part of them.

Please note that all of the configuration magics are possible when using the exec form of the ENTRYPOINT. When using the shell form of the ENTRYPOINT, you need to pass all command line arguments manually:

ENTRYPOINT exec java $JAVA_OPTS -jar app.jar $0 $@

Command line arguments

The Spring Boot automatically accepts all command line arguments and these arguments are passed into run command inside Docker:

docker build -t <image_tag> . &amp;&amp; docker run -p 8080:8080 <image_tag> --logging.level.org.springframework=debug

System properties

The similar way is using regular system properties:

docker build -t <image_tag> . &amp;&amp; docker run -p 8080:8080 --env JAVA_OPTS=-Dlogging.level.org.springframework=DEBUG <image_tag> 

Environment variables

You may use environment variables instead of system properties. Most operating systems disallow period-separated key names, but you can use underscores instead (for example, SPRING_CONFIG_NAME instead of spring.config.name). Check the documentation page for more information.

docker build -t <image_tag> . &amp;&amp; docker run -p 8080:8080 --env LOGGING_LEVEL_ORG_SPRINGFRAMEWORK=DEBUG <image_tag>

Mount your own configuration file

You may have noticed that there is a VOLUME for mounting configuration folder:

docker build -t <image_tag> . &amp;&amp; docker run -p 8080:8080 -v /opt/spring-boot/test/config:/app/config:ro <image_tag>

So your local folder /opt/spring-boot/test/config should contain the file application.properties. This is the default configuration file name and can be easily changed by setting the property 

It’s all, but your requirements may vary in many ways. I tried to solve some of the most important conditions to use Docker for Java developers. Without resolving them, it was not worth talking about using Docker for Java developers.

As mentioned above, see the project example on my GitHub with all of the mentioned code.

Some interesting links:

Share this: