My application console application is build on .net core 7 and gave error when running on docker container, several other console applications running properly but one gave problem. Docker container logs given below: Targer OS is linux. I have tried delete docker image, tried delete project and create new problem still retain. Please note that other console applications developed on .net core 7 running properly the new one gave problem that recently added.

The above error is generic error the original one is inside the output window of visual studio when this prompt occurred. By the way this was because of runtime in my docker file but there should be aspnet "red underlined" below image.

I'm also getting the same error. Any suggestion? Thanks

I would guess you are pulling a docker container without the core runtime installed. show your docker file

How to fix "The target process exited without raising as CoreCLR started event. Ensure that the target process is configured to use .NET Core. This may be expected if the target process did not run on .NET Core"

Faisal suleman 10

User's image

My application console application is build on .net core 7 and gave error when running on docker container, several other console applications running properly but one gave problem. Docker container logs given below:
User's image

Targer OS is linux. I have tried delete docker image, tried delete project and create new problem still retain. Please note that other console applications developed on .net core 7 running properly the new one gave problem that recently added.

Zhi Lv - MSFT 32,546 Reputation points Microsoft Vendor

2023-01-25T01:37:36.79+00:00

Hi @Faisal suleman

Try to use dotnet --list-sdks and dotnet --list-runtimes commands to check the installed SDK and runtime. If you can't find the specified SDK or runtime, you can find them from here, try to install them or you can re-install the Asp.net Core 7.0.0 version. Refer to this thread. Finally clear and rebuild the project or restart the application.
Faisal suleman 10 Reputation points

2023-01-25T06:38:44.9233333+00:00

Hi @Zhi Lv - MSFT

I tried there commands on cmd screenshot given below:

Actually problem is not with my windows .net core, Please note that problem is occurred during run on docker container, I attach screenshots again:

This gives in visual studio and below screenshot is in docker container logs:

If you need any further details please let me know

Thanks for Help.
Faisal suleman 10 Reputation points

2023-01-25T06:42:29.8133333+00:00

That won't help, Actually problem is with docker Linux container, Could you please let me know if you need any further details.
Favour Onwuchekwa (s5500635) 0 Reputation points

2024-01-06T06:13:48.73+00:00

what do you mean by docker container

3 answers

Faisal suleman 10 Reputation points

2023-02-15T11:17:04.7966667+00:00

The above error is generic error the original one is inside the output window of visual studio when this prompt occurred.
By the way this was because of runtime in my docker file but there should be aspnet "red underlined" below image.
Please sign in to rate this answer.

2 people found this answer helpful.
Dylan Hyslop 1 Reputation point

2023-02-28T07:36:35.82+00:00

I am haivng the exact same issue with my docker file when I try run it on linux.

Nihal Govardhan 0 Reputation points

2023-05-09T14:45:53.34+00:00

same error for me also as i am running .net 6.0
try to write the docker code manually and run them if it works tell me also

Jerome Lecerf 0 Reputation points

2023-06-09T12:58:01.43+00:00

Hi,

I solved this problem by replacing "FROM mcr.microsoft.com/dotnet/runtime:6.0 AS base" to "FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS base"

note it was working with "runtime:6.0" when I had removed my classes libraries dependencies

hope it's help
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Laura Mateus 0 Reputation points

2023-01-26T17:00:25.0666667+00:00

I'm also getting the same error. Any suggestion? Thanks
Please sign in to rate this answer.
Fatih İshak YÜZGEÇ 0 Reputation points

2024-02-20T22:37:04.92+00:00

Ben de aynı hatayı alıyorum. bir çözüm buldun mu?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Bruce (SqlWork.com) 67,916 Reputation points

2023-01-26T17:11:12.6666667+00:00

I would guess you are pulling a docker container without the core runtime installed. show your docker file
Please sign in to rate this answer.
Faisal suleman 10 Reputation points

2023-01-30T05:11:01.7966667+00:00

Here is my docker file

Nessi, Claudio 5 Reputation points

2023-08-04T10:07:59.7566667+00:00

Hi - i had the same effect/error as well. Many projects directly run with docker-support in VS, only one showed the above error. I honestly don´t know why this special one needs aspnet-runtime, but i fixed it by changing the line

FROM mcr.microsoft.com/dotnet/runtime:6.0 AS base

to

FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS base

like suggested above.

But there is another stephole: after changing the line, you have to close/open visual-studio to really get this change in the docker runtime. The reason is, that VS creates a docker-debug-container when you choose a 'Docker' launch-setting. This container is only created once, and maps your local source-directories in the container (+ the vs-debugger).

The container is destroyed automatically, when you close VS and only recreated (parsing the changed dockerfile), when you restart it.

Perhaps this helps someone - if you have an idea how to find out why the aspnet-runtime is needed, please give me a hint. The project file targets 'net6' like all the other ones. Gives me some headache...

MUSTAFA'YA SELAMLAR 0 Reputation points

2024-04-26T16:10:31.66+00:00

Exactly same silly thing ,
The container is destroyed automatically, when you close VS and only recreated (parsing the changed dockerfile), when you restart it. It happened to me also.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to fix "The target process exited without raising as CoreCLR started event. Ensure that the target process is configured to use .NET Core. This may be expected if the target process did not run on .NET Core"

3 answers

Your answer