How jpetazzo/minimage works
Main Components
a) Source Code Layer
• Source files by language (C, Go, Python, Rust, Java)
• That these are simple test programs (hello world, whatsmyip)
b) Docker Build System
• Multi-stage build configurations
• Build stages (compilation/preparation)
• Run stages (final image)
c) Image Types Classification
• Base images (Alpine, Ubuntu, Scratch, etc.)
• Language-specific images (golang, openjdk, python, rust)
• Static vs. Dynamic builds
Layer 1: Source Code
• Simple Programs
• Hello World (C, Go, Python, Rust, Java)
• WhatsMyIP (Go)
• Python Packages (PyYAML, Data Science)
Layer 2: Build Configurations
• Single-stage Builds
• Direct builds (e.g., rust-alpine)
• Multi-stage Builds
• Build Stage
• Compiler/SDK images
• Build options (static, dynamic)
• Run Stage
• Minimal runtime images
Layer 3: Final Images
• Full OS-based
• Ubuntu
• Debian
• Minimal OS
• Alpine
• Busybox
• No OS
• Scratch
Additional Notes
• Size comparison metrics between different approaches
• Notes about compatibility constraints
• Recommended combinations for each language
• Optimization techniques used in each approach