You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue outlines the development roadmap for pycontainer-build based on feature gap analysis with similar tools (Docker, Jib, ko, Buildpacks, .NET SDK containers).
🎯 High Priority Features
These features would significantly increase adoption and are critical for production use:
Why: Essential for production apps with build-time dependencies Impact: Smaller images, faster deployments Status: Not started Related: #19 (Build Features parent)
Why: Complete the platform support already started Impact: Multi-arch deployments, ARM64/Apple Silicon support Status: Not started Related: #47 (Multi-Architecture parent)
Why: Reproducible builds are essential for production Impact: Consistent deployments, compliance, security Status: Not started Related: #48 (Dependency Management parent)
Why: Common need for parameterized builds Impact: Flexible configurations for different environments Status: Not started Related: #19 (Build Features parent)
Why: Convenience for versioning workflows Impact: Simpler tagging, better version management Status: Not started Related: #57 (Registry Features parent)
This issue outlines the development roadmap for pycontainer-build based on feature gap analysis with similar tools (Docker, Jib, ko, Buildpacks, .NET SDK containers).
🎯 High Priority Features
These features would significantly increase adoption and are critical for production use:
1. Multi-Stage Builds (#20)
Why: Essential for production apps with build-time dependencies
Impact: Smaller images, faster deployments
Status: Not started
Related: #19 (Build Features parent)
2. True Cross-Compilation (#63)
Why: Complete the platform support already started
Impact: Multi-arch deployments, ARM64/Apple Silicon support
Status: Not started
Related: #47 (Multi-Architecture parent)
3. Lockfile Support (#59)
Why: Reproducible builds are essential for production
Impact: Consistent deployments, compliance, security
Status: Not started
Related: #48 (Dependency Management parent)
4. Image Signing (#13)
Why: Security requirement for enterprises
Impact: Supply chain security, compliance
Status: Not started
Related: #12 (Security & Compliance parent)
5. Remote Cache (#61)
Why: Performance in CI/CD environments
Impact: Faster builds, cost savings
Status: Not started
Related: #49 (Caching & Performance parent)
🔨 Medium Priority Features
These features enhance usability and are commonly expected:
6. Build Arguments (#21)
Why: Common need for parameterized builds
Impact: Flexible configurations for different environments
Status: Not started
Related: #19 (Build Features parent)
7. System Package Installation (#64)
Why: Many Python apps need libpq, gcc, etc.
Impact: Support for more Python packages
Status: Not started
Related: #48 (Dependency Management parent)
8. Layer Inspection Tools (#65)
Why: Debugging and optimization
Impact: Better visibility, smaller images
Status: Not started
Related: #52 (Observability parent)
9. Dockerfile Import Tool (#62)
Why: Migration path from Docker
Impact: Easier adoption, lower barrier to entry
Status: Not started
Related: #53 (Standards & Compatibility parent)
10. Multiple Tag Patterns (#60)
Why: Convenience for versioning workflows
Impact: Simpler tagging, better version management
Status: Not started
Related: #57 (Registry Features parent)
📋 Feature Categories
All features are organized into parent issues:
🗺️ Development Phases
Phase 1: Foundation (High Priority)
Phase 2: Performance & Security
Phase 3: Developer Experience
Phase 4: Ecosystem Integration
📊 Progress Tracking
🤝 Contributing
See individual issues for implementation details. High-priority items are tagged with
high-prioritylabel.📚 References