A Practical Guide to Containerizing Your Spring Boot Application
summary
Containerizing Spring Pet Clinic on Java 11 uses Dockerfiles, Dive and docker history to inspect layers, and compares builders: Dockerfile images, Cloud Native Buildpacks (pack), and JIB; images are pulled into a local registry and run successfully for functional checks. Focus is on dependency management, scanning, layer ordering and size impact on CI/CD and costs. Measured results include JRE Bullseye halved image size vs full OpenJDK 11 and JIB produced 392 MB similar to JRE, demonstrating concrete tradeoffs and the need to test the whole build pipeline.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:09INTRODUCTION
- 4:16DEVOPS TOPICS
- 23:56LAYERS
- 30:49IMAGE TAG NAMES DEMYSTIFIED
- 32:27DOCKER HISTORY
- 34:55DOCKER DESKTOP DASHBOARD
- 40:02OTHER OPTIONS FOR PARENT IMAGES
- 43:05BUILDPACKS
- 46:32SHARING IS CARING
related talks
42mCrafting the Ultimate Docker Image for Spring Applications
46mJava & Spring Boot in Containers
51mLean Spring Boot Applications for The Cloud
38mAdopt Open J9 for Spring Boot performance!
51mJava-based microservices, containers, Kubernetes - how to
39mHow to Reduce the Footprint of Your Spring Boot Applications
01h 13mSpring: Your next Java microframework
01h 12mSpring Boot "fat" JAR: The Thin Parts of a Thick Artifact