microsoft/dotnet-nightly-reverse-proxy
dotnet/nightly/reverse-proxy
Official images for the .NET Reverse Proxy (YARP)
Important: The images from the dotnet/nightly repositories include last-known-good (LKG) builds for the next release of .NET.
2.3-preview
docker pull mcr.microsoft.com/dotnet/nightly/reverse-proxy:2.3-preview
This image contains an implementation of YARP, a reverse proxy framework in .NET.
Watch discussions for Docker-related .NET announcements.
The .NET Docker samples show various ways to use .NET and Docker together. See Building Docker Images for .NET Applications to learn more.
You can run this image to launch a YARP instance.
YARP expects the config file to be in /etc/reverse-proxy.config
, and listens by default on port 5000.
Example of configuration:
{
"Logging": {
"LogLevel": {
"Default": "Information",
"Microsoft": "Warning",
"Microsoft.Hosting.Lifetime": "Information"
}
},
"AllowedHosts": "*",
"ReverseProxy": {
"Routes": {
"route1": {
"ClusterId": "cluster1",
"Match": {
"Path": "/aspnetapp/{**catch-all}"
},
"Transforms": [
{ "PathRemovePrefix": "/aspnetapp" }
]
}
},
"Clusters": {
"cluster1": {
"Destinations": {
"destination1": {
"Address": "http://aspnetapp1:8080"
}
}
}
}
}
}
It can then be used with the following command (where my-config.config
is a file containing this configuration):
docker run --rm --name myaspnetapp -d -t mcr.microsoft.com/dotnet/samples:aspnetapp
docker run --rm -v $(pwd)/my-config.config:/etc/reverse-proxy.config -p 5000:5000 --link myaspnetapp:aspnetapp1 mcr.microsoft.com/dotnet/reverse-proxy:latest
This example will proxy every requests from http://localhost:5000/aspnetapp
to the mcr.microsoft.com/dotnet/samples:aspnetapp
container deployed.
The YARP GitHub repository contains more configuration samples.
For more details, see the documentation for how to configure the image and documentation for the reverse proxy configuration.
.NET:
.NET Framework:
View the current tags at the Microsoft Artifact Registry portal or on GitHub.
.NET container images are regularly monitored for the presence of CVEs. A given image will be rebuilt to pick up fixes for a CVE when:
Please refer to the Security Policy and Container Vulnerability Workflow for more detail about what to do when a CVE is encountered in a .NET image.
docker pull mcr.microsoft.com/dotnet/nightly/reverse-proxy