anchor.diff:  For Maven, refer to the {spring-boot-maven-plugin-docs}/#repackage-layered-jars[packaging layered jars section] for more details on creating a layered jar.
   For Gradle, refer to the {spring-boot-gradle-plugin-docs}/#packaging-layered-jars[packaging layered jars section] of the Gradle plugin documentation.
   
  -==== Writing the Dockerfile
  +=== Writing the Dockerfile
   
   When you create a layered jar, the `spring-boot-layertools` jar will be added as a dependency to your jar.
   With this jar on the classpath, you can launch your application in a special mode which allows the bootstrap code to run something entirely different from your application, for example, something that extracts the layers.
  
positive.code: 
  
  [[building-docker-images]]
  === Building Docker Images
  Spring Boot applications can be containerized by packaging them into 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.
  
negative.code: 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.
  
  === Layered Jars
  To make it easier to create optimized Docker images that can be built with a dockerfile, Spring Boot supports "layered jars".
  A regular fat jar that can be run with `java -jar` has the following structure:
  
  