-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot run ASP.NET Core app using buildkit #213
Comments
It seems like BuildKit may be outputting everything to stderr instead out stdout. Our logic treats non-zero exit code as error, but also output to stderr as error. |
@pikausp We've implemented a fix which will be available with 16.4 Preview 3. It will require updating the referenced Microsoft.VisualStudio.Azure.Containers.Tools.Targets to 1.9.7, which will become available when 16.4 Preview 3 releases. It is possible that older versions of VS (e.g. I tested with 16.3) will work as long as you update the above package to 1.9.7, but, you will see failures during container warmup on project load (this warmup is just an optimization and not required to work). When you F5, it should work. If you wish to not see these failures, you can disable warmup in Tools > Options > Container tools > Single project > Run containers on project open. |
BuildKit is not supported on Windows hosts anymore. |
@bwateratmsft since you've mentioned version 1.9.7 already three months ago, may I ask whether there's any ETA when this will become available? |
Sorry for the oversight, the NuGet was published, but not publicly listed. The final version for VS 16.4 is 1.9.10 which is now publicly available |
@NCarlsonMSFT thanks, it works like a charm! I wish there was an option to set |
@sibbl That would be a new issue |
When I attempt to run the application in docker after switching to buildkit I get an error
Docker command failed with exit code 0.
Building the image from shell works as expected. I tried cleaning the solution and removing all containers & images.I removed as much as possible from the Dockerfile and now it looks like this
This is the build log
Docker desktop 2.1.0.3 (38240) (Engine v19.03.2)
VS 16.3.1
The text was updated successfully, but these errors were encountered: