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
❯ dotnet publish /p:PublishProfile=DefaultContainer
Restore complete (1.6s)
web succeeded (9.0s) → bin/Release/net9.0/publish/
Build succeeded in 11.8s
The output is exactly the same as when building the project as a (non-container) .NET app:
❯ dotnet publish
Restore complete (1.6s)
web succeeded (1.3s) → bin/Release/net9.0/publish/
Build succeeded in 4.2s
During the build, the PublishContainer show up. That is indicative of the container image being built. Once the build is finished, that message was overwritten.
With .NET 8, the base image and image being built are both shown on the terminal:
❯ dotnet publish /p:PublishProfile=DefaultContainer
MSBuild version 17.8.5+b5265ef37 for .NET
Determining projects to restore...
All projects are up-to-date for restore.
web -> /tmp/web/bin/Release/net8.0/web.dll
web -> /tmp/web/bin/Release/net8.0/publish/
Building image 'web' with tags 'latest' on top of base image 'mcr.microsoft.com/dotnet/aspnet:8.0'.
Pushed image 'web:latest' to local registry via 'podman'.
This is an expected side effect of the change to using Terminal Logger by default on .NET 9. The short term fix is to disable TL with -tl:off, but longer term TL needs to learn about:
Intermediate progress reporting
Reporting final outputs other than DLLs
Both of which we're tracking over at dotnet/msbuild.
Output after building a container image:
The output is exactly the same as when building the project as a (non-container) .NET app:
During the build, the
PublishContainer
show up. That is indicative of the container image being built. Once the build is finished, that message was overwritten.With .NET 8, the base image and image being built are both shown on the terminal:
cc @baronfel
The text was updated successfully, but these errors were encountered: