We have numerous .net core web API’s that we began building over a year ago when .net core was still in release candidate status. Because it was so new and lacking capabilities, we were compelled to continue referencing the 4.6.1 framework with the intent of eventually getting off it once .net core became more stable and feature rich. Although that day has come, we are unable to make the transition at this time, so we are still dependent on 4.6.1. We are finding that these APIs do not appear to work properly on any of the Microsoft base Docker images including aspnet, aspnetcore, dotnet, and iis. I am able to build the image and run the container without error, but when I attempt to access the API, I receive a 500 error. There are no errors in the docker log and I am not seeing any errors in the application STDOUT log. What makes these apps unique from a traditional asp.net API and .net core API is the process path. Below is an example from the published web.config.
<aspNetCore processPath=".\TestDotnetCore461WebAPI.exe" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" />
Any ideas how we can get these APIs running on Docker would be greatly appreciated.