You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Echoing this - the container tests are in kind of an odd space (at least for the preview timeframe). The SDK version being used to build containers carries along a certain RuntimeFrameworkVersion implicitly, but the containers made available on mcr.microsoft.com lag behind in terms of the runtimes installed on them (by design - they are only made in the run-ups to each preview release) and so in the SDK we tend to make framework-dependent apps that we actually can't run in containers. We (containers team) need a better strategy for this and so I added these properties to 'pin' the runtimes for projects targeting net8.0 as a temporary measure.
Originally posted by @baronfel in #30038 (comment)
We (@dotnet/sdk-container-builds-maintainers) need some kind of testing strategy that is resilient to this timing issue.
The text was updated successfully, but these errors were encountered: