Add Blazor gateway container image - #7314
Open
javiercn wants to merge 3 commits into
Open
Conversation
javiercn
marked this pull request as ready for review
August 19, 2026 10:09
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
javiercn
force-pushed
the
javiercn-blazor-gateway-image-plan
branch
from
August 19, 2026 10:09
0449f75 to
84f49c8
Compare
lbussell
reviewed
Aug 21, 2026
| "aspnet|11.0|build-version": "11.0.0-preview.7.26381.103", | ||
| "aspnet-composite|11.0|build-version": "$(aspnet|11.0|build-version)", | ||
|
|
||
| "blazor-gateway|11.0|build-version": "11.0.0-preview.7.26381.103", |
Member
There was a problem hiding this comment.
Is it always the same version as aspnet, and always ships with aspnet (from the VMR)? If so, we can just re-use the version.
Comment on lines
+15
to
+18
| * `ClientApps` — the set of Blazor applications the gateway serves, including each application's endpoints manifest location and path prefix. | ||
| * `ReverseProxy` — standard [YARP](https://aka.ms/YarpDocumentation) reverse-proxy routes and clusters, used to proxy requests to backend APIs alongside the Blazor application(s). | ||
| * Service discovery — the gateway uses [.NET service discovery](https://learn.microsoft.com/dotnet/core/extensions/service-discovery) to resolve destination addresses for reverse-proxy clusters. | ||
| * `Gateway` — gateway-level settings. |
Member
There was a problem hiding this comment.
Suggested change
| * `ClientApps` — the set of Blazor applications the gateway serves, including each application's endpoints manifest location and path prefix. | |
| * `ReverseProxy` — standard [YARP](https://aka.ms/YarpDocumentation) reverse-proxy routes and clusters, used to proxy requests to backend APIs alongside the Blazor application(s). | |
| * Service discovery — the gateway uses [.NET service discovery](https://learn.microsoft.com/dotnet/core/extensions/service-discovery) to resolve destination addresses for reverse-proxy clusters. | |
| * `Gateway` — gateway-level settings. | |
| * `ClientApps`: the set of Blazor applications the gateway serves, including each application's endpoints manifest location and path prefix. | |
| * `ReverseProxy`: standard [YARP](https://aka.ms/YarpDocumentation) reverse-proxy routes and clusters, used to proxy requests to backend APIs alongside the Blazor application(s). | |
| * Service discovery: the gateway uses [.NET service discovery](https://learn.microsoft.com/dotnet/core/extensions/service-discovery) to resolve destination addresses for reverse-proxy clusters. | |
| * `Gateway`: gateway-level settings. |
Comment on lines
+23
to
+28
| docker run --rm -p 8080:8080 \ | ||
| -v $(pwd)/myapp/wwwroot:/app/wwwroot:ro \ | ||
| -v $(pwd)/myapp/MyApp.staticwebassets.endpoints.json:/app/myapp.endpoints.json:ro \ | ||
| -e ClientApps__myapp__EndpointsManifest=/app/myapp.endpoints.json \ | ||
| -e ClientApps__myapp__PathPrefix= \ | ||
| {{FULL_REPO}}:{{if VARIABLES["branch"] = "nightly":11.0-preview^else:latest}} |
Member
There was a problem hiding this comment.
This is a really strange way to recommend deploying an app. I don't suspect many users will actually deploy their app this way.
I think most would expect to build a Dockerfile, push it somewhere, and then deploy that.
| @@ -0,0 +1,35 @@ | |||
| ARG REPO=mcr.microsoft.com/dotnet/aspnet | |||
Member
There was a problem hiding this comment.
The gateway is supposed to be "an optimized host for deploying standalone Blazor apps". Yet it includes the whole ASP.NET Runtime. Can it be a Native AOT app instead?
I, as a user, do not understand why I should use the gateway over building my app with Yarp and app.UseStaticFiles() in my own Dockerfile. Or just nginx.
Comment on lines
+13
to
+15
| RUN gateway_version=0.0.0 \ | ||
| && curl --fail --show-error --location --output blazor_gateway.nupkg https://globalcdn.nuget.org/packages/microsoft.aspnetcore.components.gateway.cli.$gateway_version.nupkg \ | ||
| && blazor_gateway_sha512='{sha512_placeholder}' \ |
Member
There was a problem hiding this comment.
When ASP.NET or Blazor gateway has security fixes, how do we get an internal pre-release version of the gateway?
Comment on lines
+22
to
+24
| blazor-gateway/ @dotnet/dotnet-docker-reviewers | ||
| *blazor-gateway* @dotnet/dotnet-docker-reviewers | ||
| *Blazor-Gateway* @dotnet/dotnet-docker-reviewers |
|
|
||
| ```bash | ||
| docker run --rm -p 8080:8080 \ | ||
| -v $(pwd)/myapp/wwwroot:/app/wwwroot:ro \ |
Member
There was a problem hiding this comment.
Using $(pwd) like this doesn't work on Windows/PowerShell.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
mcr.microsoft.com/dotnet/nightly/blazor-gatewayfor .NET 11 preview on Azure Linux 3.0 distroless amd64 and arm64Microsoft.AspNetCore.Components.Gateway.Cli, retaining only the runtime payload and third-party noticesStable
mcr.microsoft.com/dotnet/blazor-gatewaypublication is intentionally deferred until .NET 11 RTM.Validation
pwsh -NoProfile ./tests/run-tests.ps1 -paths '*blazor-gateway*' -TestCategories @('pre-build')(159 passed)pwsh -NoProfile ./build-and-test.ps1 -mode 'Build' -paths '*blazor-gateway*'pwsh -NoProfile ./tests/run-tests.ps1 -paths '*blazor-gateway*' -TestCategories @('blazor-gateway')(6 passed)linux/arm64Docker build against the nightly ASP.NET base