Docker Container Loading
summary
Dockerfile works but has limits: you cannot parameterize FROM, you cannot include reusable fragments, and each command forces a layer. Alternatives shown include fish-pepper (Node.js templates that generate permutations for OS/JDK/version combinations and include file/fragments), Ansible Container (runs Ansible against ephemeral containers then does one final docker commit producing a single-layer image, slower but reproducible), Rocker (Dockerfile extensions with mount caching and export/import), Packer, Maven plugins, Docker Hub CI, Google Cloud Build (cloudbuild.yaml steps push to GCR) and OpenShift s2i (builder image assembles and commits, runs non-root).
AI-written summary · about
chapters (13)
- 0:00Docker image creation intro
- 1:27Canonical Docker image creation
- 3:16Dockerfile limitations
- 7:29Fish Pepper templating
- 13:08Ansible Container builds
- 18:46Packer multi-platform images
- 22:14Rocker Dockerfile extensions
- 26:08Maven Docker integration
- 34:33Cloud Docker image services
- 37:25Docker Hub CI builds
- 41:17Google Container Builder
- 45:55OpenShift Source-to-Image
- 54:00Summary & Q&A
related talks
54mHowto: Options Galore to Get from Source Code to Container
34mDefence Against the Docker Arts
58mOptions Galore to Get from Source Code to Container
29mDockerfile: the best practices
46mDockerfiles, Buildpacks, Jib and more, best way to run Java code in Containers?
46mWrite Once, Run Anywhere? Building Perfect Docker Images for Java Apps
51mProduction level Docker
30mDockerfile - Best Practices