- Created structured documentation with /patterns/, /examples/, and /reference/ directories - Implemented automatic context loading rules in CLAUDE.md based on file extensions, directories, and keywords - Added technology-specific patterns for Docker, Python, Node.js, Vue.js, Bash, networking, databases, and VM management - Included complete working examples for common workflows and troubleshooting references - Designed for minimal context usage with precise loading triggers 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
26 lines
942 B
Markdown
26 lines
942 B
Markdown
# Docker Patterns
|
|
|
|
## Container Best Practices
|
|
- Use multi-stage builds for production images
|
|
- Minimize layer count and image size
|
|
- Run containers as non-root users
|
|
- Use specific version tags, avoid `latest`
|
|
- Implement health checks
|
|
|
|
## Common Patterns
|
|
- **Multi-service applications**: Use docker-compose for local development
|
|
- **Production deployments**: Single-container per service with orchestration
|
|
- **Development environments**: Volume mounts for code changes
|
|
- **CI/CD integration**: Build, test, and push in pipeline stages
|
|
|
|
## Security Considerations
|
|
- Scan images for vulnerabilities
|
|
- Use distroless or minimal base images
|
|
- Implement resource limits
|
|
- Network isolation between services
|
|
|
|
## Related Documentation
|
|
- Examples: `/examples/docker/multi-stage-builds.md`
|
|
- Examples: `/examples/docker/compose-patterns.md`
|
|
- Reference: `/reference/docker/troubleshooting.md`
|
|
- Reference: `/reference/docker/security-checklist.md` |