From 30b5168fed81d3a0dd53af280b8d1902effb280c Mon Sep 17 00:00:00 2001 From: Stephane Nicoll Date: Thu, 16 Jul 2020 16:15:50 +0200 Subject: [PATCH] Polish "Restructure "Building Container Images" section" See gh-22296 --- .../src/docs/asciidoc/deployment.adoc | 2 +- .../src/docs/asciidoc/spring-boot-features.adoc | 12 ++++++++---- 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/deployment.adoc b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/deployment.adoc index a7c41e3b3067..5590700a5674 100644 --- a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/deployment.adoc +++ b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/deployment.adoc @@ -36,7 +36,7 @@ Once you have unpacked the jar file, you can also get an extra boost to startup NOTE: Using the `JarLauncher` over the application's main method has the added benefit of a predictable classpath order. The jar contains a `classpath.idx` file which is used by the `JarLauncher` when constructing the classpath. -More efficient container images can also be created by <> for your dependencies and application classes and resources (which normally change more frequently). +More efficient container images can also be created by <> for your dependencies and application classes and resources (which normally change more frequently). diff --git a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/spring-boot-features.adoc b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/spring-boot-features.adoc index 1c5c6d59d0e0..d2ad49ba0dd4 100644 --- a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/spring-boot-features.adoc +++ b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/spring-boot-features.adoc @@ -8176,11 +8176,13 @@ If you need the `Mockk` equivalent of the Mockito specific <>, or by <>. +Spring Boot applications can be containerized either by <>, or by <>. + + -[[building-docker-images]] +[[boot-features-container-images-docker]] === Building Docker images A typical Spring Boot fat jar can be converted into a Docker image by adding just a few lines to a Dockerfile that can be used to build the image. However, there are various downsides to copying and running the fat jar as is in the docker image. @@ -8189,6 +8191,8 @@ The other issue is that putting your application's code and all its dependencies Since you probably recompile your code more often than you upgrade the version of Spring Boot you use, it’s often better to separate things a bit more. If you put jar files in the layer before your application classes, Docker often only needs to change the very bottom layer and can pick others up from its cache. + + ==== Layering Docker Images To make it easier to create optimized Docker images that can be built with a dockerfile, Spring Boot supports adding a layer index file to the jar. It provides a list of layers and the parts of the jar that should be contained within them. @@ -8284,7 +8288,7 @@ Of course, a Dockerfile can be written without using the jarmode. You can use some combination of `unzip` and `mv` to move things to the right layer but jarmode simplifies that. -[[using-buildpacks]] +[[boot-features-container-images-buildpacks]] === Buildpacks Dockerfiles are just one way to build docker images. Another way to build docker images is directly from your Maven or Gradle plugin, using buildpacks.