Registry Resilience

Registry Resilience Registry Resilience

This release focuses on improving reliability, synchronization, and system stability. The headline feature is multiple backup registry support, which allows developers to define fallback registries and maintain uninterrupted builds even when a primary source becomes unavailable. This enhancement ensures smoother CI/CD pipelines and reduces downtime caused by external registry issues.

Another key addition is runner domain synchronization, which keeps sandbox container domains aligned across states. This improvement eliminates discrepancies between expected and actual runtime environments, providing more consistent results for teams running large or distributed workloads.

The release also introduces a new config endpoint for both the API and dashboard, giving developers greater visibility into runtime configuration. This makes integration and troubleshooting more straightforward, especially when managing complex setups.

On the stability side, daemon error handling has been upgraded to return controlled errors instead of triggering fatal crashes, strengthening overall resilience. Additionally, runner working directory resolution now derives directly from container config, avoiding failures when images are not yet pulled.

Together, these updates enhance Daytona’s reliability at every layer. Registries, runners, and core services, ensuring developers can focus on building without interruptions or unexpected failures.

Release Details

  • multiple backup registry support (#2396)

  • sync runner domain states (#2419)

  • add docker-compose setup (ea0b7205)

  • api, dashboard: config endpoint (56d9ce26)

Bug fixes

  • daemon: Return error instead of calling log.Fatal (#2413)

  • runner: get WorkingDir from container config to avoid inspecting unpulled images (#2452)