Description
AddFoundry(...).RunAsFoundryLocal() fails immediately on Foundry Local CLI 0.10.x because the hosting integration still invokes foundry service, which was removed in the CLI 0.10 rewrite.
The Foundry resource goes to FailedToStart. Any deployment (AddDeployment) never starts. Resources that WaitFor that deployment stay Waiting (kernel/app deadlock).
Repro
- Install Foundry Local CLI 0.10.3 (
foundry --version → 0.10.3). Confirm:
Command groups include server, not service.
- AppHost:
var foundry = builder.AddFoundry("foundry").RunAsFoundryLocal();
var whisper = foundry.AddDeployment("whisper-large-v3-turbo", "whisper-large-v3-turbo", "1", "OpenAI");
builder.AddProject<Projects.MyApp>("app").WaitFor(whisper);
aspire start (or F5).
Actual
Foundry resource console:
error: Unknown command: 'service'
Hint: Did you mean 'server'? Run 'foundry --help' to see available commands.
Foundry Local could not be started. Ensure it's installed correctly: https://learn.microsoft.com/azure/ai-foundry/foundry-local/get-started (Error: Foundry CLI service exited before reporting an endpoint. Exit code: 2.).
Expected
RunAsFoundryLocal should start the daemon with the current CLI:
| Old CLI (≤0.8) |
CLI 0.10+ |
foundry service start/stop/restart |
foundry server start/stop/restart |
Documented in:
Aspire docs still say foundry service start:
https://aspire.dev/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host/
Environment
- Aspire CLI: 13.5.3
Aspire.Hosting.Foundry: 13.5.3-preview.1.26425.3- Foundry Local CLI: 0.10.3 (
foundry server, foundry transcribe, no foundry service)
- OS: Windows 11 x64
- AppHost: .NET 11 / Aspire 13.5.3
Related
Suggested fix
Detect CLI version / help output and call foundry server start on 0.10+, keep foundry service start as fallback for older CLIs. Update hosting docs to match CLI 0.10.
Description
AddFoundry(...).RunAsFoundryLocal()fails immediately on Foundry Local CLI 0.10.x because the hosting integration still invokesfoundry service, which was removed in the CLI 0.10 rewrite.The Foundry resource goes to FailedToStart. Any deployment (
AddDeployment) never starts. Resources thatWaitForthat deployment stay Waiting (kernel/app deadlock).Repro
foundry --version→0.10.3). Confirm:Command groups include
server, notservice.aspire start(or F5).Actual
Foundry resource console:
Expected
RunAsFoundryLocalshould start the daemon with the current CLI:foundry service start/stop/restartfoundry server start/stop/restartDocumented in:
Aspire docs still say
foundry service start:https://aspire.dev/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host/
Environment
Aspire.Hosting.Foundry: 13.5.3-preview.1.26425.3foundry server,foundry transcribe, nofoundry service)Related
WaitForhangs if Foundry Local never becomes Running (same cascade once this start fails).openai-whisper-large-v3-turbo-cuda-gpufoundry-local#458 — CLI still does not run voice models (Whisper is SDK-only). Separate from this command rename;AddDeployment(whisper-*)would still be the wrong path even afterservice→server.Suggested fix
Detect CLI version / help output and call
foundry server starton 0.10+, keepfoundry service startas fallback for older CLIs. Update hosting docs to match CLI 0.10.