AddRazorRuntimeCompilation fails with chiseled image mcr.microsoft.com/dotnet/aspnet8.0.1:-jammy-chiseled-extra

[marc-mueller]

I wanted to use a chiseled image to run an ASP.NET Core 8 application which uses Razor runtime compilation to load views from a database. However, when starting the application, there is an error like this:

An exception was thrown while activating Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionEndpointDataSourceFactory 
 Microsoft.AspNetCore.Mvc.Infrastructure.DefaultActionDescriptorCollectionProvider 
 Microsoft.AspNetCore.Mvc.Infrastructure.IActionDescriptorChangeProvider[] 
 Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation.PageActionDescriptorChangeProvider 
 
:Microsoft.AspNetCore.Razor.Language.RazorProjectEngine.","Attributes":{"Method":"GET","Path":"/health/startup","Message":"An exception was thrown while activating Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionEndpointDataSourceFactory 
 Microsoft.AspNetCore.Mvc.Infrastructure.DefaultActionDescriptorCollectionProvider 
 Microsoft.AspNetCore.Mvc.Infrastructure.IActionDescriptorChangeProvider[] 
 Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation.PageActionDescriptorChangeProvider 
 
:Microsoft.AspNetCore.Razor.Language.RazorProjectEngine.","{OriginalFormat}":"Error occurred in {Method}:{Path} - {Message}"},"Exception":{"Message":"An exception was thrown while activating Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionEndpointDataSourceFactory 
 Microsoft.AspNetCore.Mvc.Infrastructure.DefaultActionDescriptorCollectionProvider 
 Microsoft.AspNetCore.Mvc.Infrastructure.IActionDescriptorChangeProvider[] 
 Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation.PageActionDescriptorChangeProvider 

I assume that there is a dependency missing in the chiseled image. I assumed that the ASP.NET Core runtime is the same as in the standard ASP.NET Core runtime image. Does anyone know what the missing dependency is and if it can be solved to be able to use chiseled images for this solution?

Thanks for your help!
Marc

[marc-mueller]

After having some detailed analysis I was able to reproduce it in the ASP.NET Core 8 runtime image as well. Seems to be an issue related to some general dependency issues. I need to investigate further.