Daytona server start health check doesn't wait for everything to start

[Tpuljak]

Describe the bug
The daytona server process only waits for the API server to start before exiting the command. This is problematic because the startup process also includes booting up the providers, the local registry and the headscale server which might fail or not be up soon enough for the user to interact with.

To Reproduce
Steps to reproduce the behavior:

1. Run daytona server -y && daytona provider ls
2. Observe that no providers are listed
3. Wait a few seconds
4. daytona provider ls
5. Observe that providers are present not

Expected behavior
The daytona server command should make sure that all the components have started successfully before exiting the command. This will ensure that the user is fully informed about the state of the server upon completion.

Desktop (please complete the following information):

• OS: any
• Daytona Version: v0.45.0

[Tpuljak]

@quest-bot stash 40

[quest-bot]

New Quest!

A new Quest has been launched in @daytonaio’s repo.
Merge a PR that solves this issue to loot the Quest and earn your reward.

---

Loot of 40 USD has been stashed in this issue to reward the solver!

🗡 Comment @quest-bot embark to check-in for this Quest and start solving the issue. Other solvers will be notified!

⚔️ When you submit a PR, comment @quest-bot loot #1357 to link your PR to this Quest.

Questions? Check out the docs.

---

👉 If no one is assigned to the issue, you are welcome to embark on the quest and tackle it without confirmation from us. In the event that multiple PRs are made from different people, we will generally accept those with the cleanest code.

[Freedisch]

I will take a look at it

[Freedisch]

@quest-bot embark

[quest-bot]

@Freedisch has embarked on their Quest. 🗡

• @Freedisch has been on GitHub since 2021.
• They have merged 79 public PRs in that time.
• Their swords are blessed with Dockerfile and Shell magic ✨
• They haven't contributed to this repo before.

This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.

Questions? Check out the docs.

[Ximax80]

embark

[Ximax80]

@quest-bot loot #1357

[quest-bot]

⚠️ Oops... You can only loot in a Pull Request!

Check the docs for more info.

[quest-bot]

🧚 @Ximax80 has submitted PR #1371 and is claiming the loot.

Keep up the pace, or you'll be left in the shadows.

cc @Freedisch

Questions? Check out the docs.

[naaa760]

@quest-bot embark

[quest-bot]

@naaa760 has embarked on their Quest. 🗡

• @naaa760 has been on GitHub since 2024.
• They have merged 4 public PRs in that time.
• Their swords are blessed with JavaScript and TypeScript magic ✨
• They haven't contributed to this repo before.

This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.

Questions? Check out the docs.

[Freedisch]

@Tpuljak
I have run different tests to reproduce the error on the latest build of daytona, and providers are always being listed when running either
daytona server -y && daytona provider ls or daytona provider ls

I'm going to run the tests with more components

System: Darwin arm64

[Tpuljak]

@Freedisch it fails for me basically every time. Maybe try by installing more providers first (daytona provider install)

[tarunrajput]

@quest-bot embark

[quest-bot]

@tarunrajput has embarked on their Quest. 🗡

• @tarunrajput has been on GitHub since 2017.
• They have merged 93 public PRs in that time.
• Their swords are blessed with JavaScript and CSS magic ✨
• They have contributed to this repo before.

This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.

Questions? Check out the docs.

[quest-bot]

🧚 @tarunrajput has submitted PR #1419 and is claiming the loot.

Keep up the pace, or you'll be left in the shadows.

cc @Freedisch
@Ximax80
@naaa760

Questions? Check out the docs.