Community Hours #22: Custom Builder Images
In this week's Daytona Community Hours, we discussed recent releases, upcoming features, and addressed several community issues. Let's dive into the highlights of what's new and what's on the horizon.
Recent Release: Version 0.45.0
This release introduced two main improvements:
Server Log Rotation: Implemented by Luka, this feature addresses issues with server logs. Logs are now rotated based on configurable settings, with defaults set to rotate every 100MB and retain logs for 15 days.
Provider Installation Sorting: Fixed the randomization of the Daytona provider install list, now consistently sorting providers by name for a better user experience.
Upcoming Features and Changes
Custom Builder Image Support
A significant PR is in progress to allow users to configure their own image for the entire workspace build process. This change will:
Extend the use of custom builder images beyond pre-builds to the entire creation process.
Utilize container registry credentials for pulling custom images, addressing issues with enforced sign-ins on Docker environments.
Require updates to all providers after release.
Multiple Compose Files in Dev Containers
A fix is coming to handle multiple docker-compose files in dev container configurations, improving flexibility for users with complex setups.
Server Log File Selection
Luca has implemented a feature allowing users to select and read specific log files from the server, including rotated logs.
Provider Requirement Handling
A breaking change is coming that will allow providers to define and check their requirements (e.g., Docker for the Docker provider). This will improve user experience by clearly communicating necessary dependencies.
Community Issues and Bounties
Non-interactive Git Provider Addition: An issue has been raised to support adding Git providers without going through the interactive terminal interface.
Windows and OSX Daytona Workspaces: Two significant bounty issues ($500 each) have been posted for implementing Daytona workspaces on Windows and OSX.
Environment Variable Masking: A feature request to make environment variable display optional in workspace creation logs to prevent leaking sensitive information.
Ongoing Refactoring
A major refactoring effort is underway to improve consistency, user experience, and the overall concept of workspaces and targets in Daytona. This will allow for reusing targets across multiple workspaces, significantly improving efficiency for cloud-based setups.
Conclusion
Daytona continues to evolve with a focus on improving user experience, expanding provider support, and enhancing security features. The upcoming custom builder image support and provider requirement handling promise to offer users more flexibility and clarity in their development environments.
With exciting bounty programs and ongoing refactoring efforts, the Daytona team is actively engaging the community in shaping the future of the platform. Stay tuned for more updates and opportunities to contribute to Daytona's growth.