Providing and Supporting Docker Images
summary
Elastic builds and hosts its own Docker registry because Docker Hub lacks reliability and download analytics, and images move from Alpine to CentOS 7 for JVM and corporate compatibility. Images stop startup if run as root and enforce file-handle and bootstrap checks; certificates are prebuilt for now. Tags get overwritten (tags are not immutable), multistage builds and pinned JVMs shrink images, and orchestration testing focuses on Kubernetes and Docker Compose rather than full managed integrations.
AI-written summary · about
chapters (21)
- 0:00Introduction and context
- 3:37Meaning of official Docker images
- 8:12Choosing base images
- 10:00Red Hat vs Alpine base images
- 13:10Image size trade-offs
- 16:00Future image versions and formats
- 18:25Windows containers and latest tag
- 21:38Tag immutability and security updates
- 24:04Running as root and security checks
- 27:33Default credentials and TLS certificates
- 28:59Support challenges and permissions
- 31:52Docker resource limits
- 33:39Combining Docker and Elasticsearch
- 35:27Orchestration systems
- 38:55Docker best practices and warnings
- 40:00Should you run Elasticsearch in Docker?
- 41:04Building and testing Docker images
- 43:40Pre-release testing and CI
- 46:11Docker Compose examples
- 47:56Continuous integration for images
- 49:00Conclusion and Q&A
related talks
51mProduction level Docker
40m"Willy Wonka and the Secure Container Factory"
51mDocker for developers and ops
20mEmerging Automated License Compliance for Containers
34mDefence Against the Docker Arts
39mDocker Basics
33mDocker Container Lifecycles – Problem or Opportunity?
49mContinuous Delivery at Docker age