microsoft
Func: Failed to start the inproc6 model host
Just installed this tool in vscode and trying to connect it to one of my storage accounts.
When trying to start the Durable Function Monitor it renders an immediate error with:
Func: Failed to start the inproc6 model host. An error occurred trying to start process
'/opt/homebrew/Cellar/azure-functions-core-tools@4/4.0.7030/in-proc6/func' with working directory
'/Users/<redacted>/.vscode/extensions/durablefunctionsmonitor.durablefunctionsmonitor-6.6.0/backend'.
Permission denied
I have tried connecting using both the "Durable Functions" toolbar, and using the direct connection trough Command Pallette > Durable Functions Monitor
@Cnordbo , are you able to run any .NET InProc Functions projects on this machine?
Come to think of it, its an M1 mac. Which is just to say, yes, i can run both inProc and Isolated. BUT, i do have to use a specific Nuget package in my projects for it do work.
Ref: https://github.com/microsoft/durabletask-dotnet/issues/93
But the error message does not reflect that this should be the issue here. As its giving me a "permission denied" rather than the gRPC error which is usually associated with the function app not starting if i forget to include the workaround.
I ended up using the Docker image for now which worked flawlessly.
i can run both inProc
When you run a normal .NET InProc function - does the full path to 'func' program match the path DfMon extension reports?
Can you share full outputs of DfMon extension and your test .NET InProc function (omitting anything sensitive)?
@Cnordbo , do you still need further help on this?
Hi, sorry, i just ended up running it trough the docker image. So haven't debugged this further.
Do you still want the logs?
Anyway, good to know that docker image works for you. Closing this for inactivity. Feel free to open another issue, if anything else missing.
There is an option in the VSCode setting for DurableFunctions that allows you to specify the path of the func.exe. This is what fixed things for me after installing with brew.
Battling this same issue right now (Mac M4).
Simple fix is to give anyone permissions to the the homebrew directory that is throwing the issue.
sudo chmod -R 777 [path]
But I'm not a fan (security risks).
