Failed to launch process for service - No such file or directory
See original GitHub issueTye stopped working after update, which should not affect this.
I installed the latest preview of .NET 6 SDK Preview 7 x64 on my M1 Mac, and updated the Tye Global tools like so:
robert@RobertsMBPWork Commerce % dotnet tool update -g Microsoft.Tye --version "0.9.0-*" --add-source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet5/nuget/v3/index.json
Tool 'microsoft.tye' was reinstalled with the latest stable version (version '0.9.0-alpha.21380.1').
My projects is targeting .NET 5:
I ran tye run
:
[11:23:55 INF] watch: commerce-api_bf824114-7 Started
[11:23:55 ERR] Failed to launch process for service commerce-api_bf824114-7
System.ComponentModel.Win32Exception (2): No such file or directory
at System.Diagnostics.Process.ForkAndExecProcess(String filename, String[] argv, String[] envp, String cwd, Boolean redirectStdin, Boolean redirectStdout, Boolean redirectStderr, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec)
at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
at Microsoft.Tye.ProcessUtil.RunAsync(String filename, String arguments, String workingDirectory, Boolean throwOnError, IDictionary`2 environmentVariables, Action`1 outputDataReceived, Action`1 errorDataReceived, Action`1 onStart, Action`1 onStop, CancellationToken cancellationToken) in /_/src/Microsoft.Tye.Core/ProcessUtil.cs:line 147
at Microsoft.DotNet.Watcher.DotNetWatcher.WatchAsync(ProcessSpec processSpec, IFileSetFactory fileSetFactory, String replica, CancellationToken cancellationToken) in /_/src/Microsoft.Tye.Hosting/Watch/DotNetWatcher.cs:line 72
at Microsoft.Tye.Hosting.ProcessRunner.<>c__DisplayClass8_0.<<LaunchService>g__RunApplicationAsync|0>d.MoveNext() in /_/src/Microsoft.Tye.Hosting/ProcessRunner.cs:line 380
[11:23:55 INF] Tye Host is stopping...
My projects targets .NET 5:
My global.json
:
{
"sdk": {
"version": "5.0.400"
}
}
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Cannot run Tye with Dapr on WSL2 · Issue #795 · dotnet/tye
When I use tye run on WSL2 (Ubuntu 20) with dapr, the system throws an exception [16:36:32 ERR] Failed to launch process for...
Read more >Visual Studio Code terminal is failing to launch
I tried to compile a program, but the terminal is not opening. error:The terminal process failed to launch: Starting directory (cwd) "D:\vs code ......
Read more >Systemd cannot exec a start command with error: No such ...
I tried to su into the nomifactory user to execute the command specified in ExecStart in the same directory as specified in WorkingDirectory ......
Read more >Failed to spawn mysql main process: unable to execute
First make a backup of your /var/lib/mysql/ directory just to be safe. ... (only run these if the files are no longer there)...
Read more >Troubleshooting Windows Subsystem for Linux
Provides detailed information about common errors and issues people run into while running Linux on the Windows Subsystem for Linux.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I uninstalled both NET 6 SDK Preview 6 and 7, and it works again.
Doesn’t seem to play well with Tye at the moment.
I think this is because of the change to revert the AppHost as the default build output for MacOS. Project Reading derives the
RunCommand
from build metadata here, which should be the apphost executable, but on MacOS on .NET 6+ we do not create the AppHost due to signing issues. This means that the RunCommand is incorrect, and thus the service cannot be launched.