Description

It looks like the problem describred in #666707, is happening in .NET 9

More details

Application description

Containerized .net 9 console app, built from worker service template

If some configuration is missing, the app throws an exception in a constructor of a DI injected service.

Behavior in Windows Docker Desktop

When running
docker run myapp:1.0
the container stops as a consequence of the unhandled exception

Behavior in Linux docker - Unexpected behavior!!

When running
docker run myapp:1.0
the container shows the unhandled exception, but doesn't stop

However, adding the --init switch:
docker run --init myapp:1.0
the container shows the excception, and stops, as expected

Summary

So it looks exactly as described in #66707 (comment)

Reproduction Steps

As described above:

• containerized app throwing an exception (more specifically an app based on worker service template throwing in the ctor of an injected service)

Running it in Linux ARM64 with
docker run myapp:1.0
doesn't stop the container

Adding --init, the exception does stop the container.

Expected behavior

Running the contaienr in Linux ARM64 with
docker run myapp:1.0
shoudl stop the contaienr on unhandled exception, but only does if --init is added.

Actual behavior

The container doesn't stop on unhandled exception.

Regression?

If it was really fixed in .NET 7, yep, it's a regression of something solved as explained in #66707

Known Workarounds

Run the container with --init

Configuration

No response

Other information

No response