foundry model list, No models were returned from the Azure Foundry catalog.

[TheNotary]

Hello,

It's a little unclear from the docs, but is foundry model list meant to list models available from the Foundry model catalog? I freshly installed today via winget, and here's how my session with the CLI went.

PS >  foundry service list
🟢 Service is Started on http://127.0.0.1:59092/, PID 47804!
No models are currently loaded in the service
PS >  curl http://127.0.0.1:59092/
PS >  curl http://127.0.0.1:59092/v1/models
{"data":[],"IsDelta":false,"Successful":true,"HttpStatusCode":0,"object":"list"}

PS >  foundry model list
🕑 Downloading complete!...
Successfully downloaded and registered the following EPs: QNNExecutionProvider.
Valid EPs: CPUExecutionProvider, QNNExecutionProvider
[13:51:41 WRNException: No models were returned from the Azure Foundry catalog.
] Failed: Fetching model list from Foundry Catalog

PS >  foundry model run phi-3-mini-4k
[13:59:12 ERR] Failed to process model #0 on page 1.
[13:59:12 ERR] Failed to process model #0 on page 1.
[13:59:12 ERR] Failed to process model #0 on page 1.
[13:59:12 ERR] Failed to process model #0 on page 1.
[13:59:12 WRN] Failed: Fetching model list from Foundry Catalog
Exception: No models were returned from the Azure Foundry catalog.

Install Command:

>  winget install Microsoft.FoundryLocal
Found Foundry Local [Microsoft.FoundryLocal] Version 0.8.119.102
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
This package requires the following dependencies:
  - Packages
      Microsoft.VCLibs.Desktop.14 [>= 14.0.33728.0]
Successfully verified installer hash
Starting package install...
  ██████████████████████████████  100%
Successfully installed

[wesalexander]

Seeing a similar issue on a fresh install (0.8.119) via winget (winget install Microsoft.FoundryLocal) on 25H2 (26200.8457) and 25H2 (26200.8390).

Additionally, attempted to roll back to 0.8.117.0 which yielded the same results which ultimately leads me to believe there is a fundamental issue with the endpoint where the models are being retrieved.

[bmehta001]

Hi @TheNotary and @wesalexander, Thanks for raising this issue. This is likely due to the issue described in #757.

Using Foundry Local SDK v1.2.0 as described in that issue will likely mitigate your issues. Please comment on #757, if you still experience issues even after trying out samuel100's steps

[TheNotary]

Hmm.. as far as I can tell, I have the latest version published to winget. When I run foundry --version on the CLI, I get 0.8.119 as the output, so it's hard for me to tell if there is a packaging issue at play here also. Is the winget package not being updated correctly during the release cycle by any chance? That would explain the --version outputs and things not working on our end after a fresh install.

[anch-msft]

Also seeing this issue on foundry local 0.8.119, which is the latest available through winget.

[karpediemnow]

I found the same issue a workaround is to copy in a local folder %USERPROFILE%.foundry\cache\models the following file:

foundry.modelinfo.json

Waiting the update of winget installation :|

[tjohnson-l20]

I have not tried @karpediemnow's work around but can confirm as a first-time user installing the latest version on my machine using winget today, I get the same errors.

[13:14:32 ERR] Failed to process model #0 on page 1.
[13:14:32 WRN] Failed: Fetching model list from Foundry Catalog

[Matt-Mcl]

I found the same issue a workaround is to copy in a local folder %USERPROFILE%.foundry\cache\models the following file:

foundry.modelinfo.json

Waiting the update of winget installation :|

@karpediemnow

This doesn't seem to work for me?

Edit: Nevermind! Just needed to run foundry service restart after copying this file to the relevant location

[lexcyn]

I found the same issue a workaround is to copy in a local folder %USERPROFILE%.foundry\cache\models the following file:

foundry.modelinfo.json

Waiting the update of winget installation :|

Seeing the same here on a fresh install via winget - but copying that file into the folder and restarting the foundry service did resolve the issue, but strange.