.NET Monitor Tool

Important: The images from the dotnet/nightly repositories include last-known-good (LKG) builds for the next release of .NET.

See dotnet for images with official releases of .NET.

Featured Tags

9 (Standard Support)
- docker pull mcr.microsoft.com/dotnet/nightly/monitor:9
8 (Long-Term Support)
- docker pull mcr.microsoft.com/dotnet/nightly/monitor:8

About

This image contains .NET Monitor, a diagnostic tool for capturing diagnostic artifacts (such as dumps and traces) in an operator-driven or automated manner. This tool is an ASP.NET application that hosts a web API for inspecting .NET processes and collecting diagnostic artifacts. This image also contains .NET Monitor extensions for egressing artifacts to Azure Blob Storage and Amazon S3.

Watch discussions for Docker-related .NET announcements.

Usage

The .NET Docker samples show various ways to use .NET and Docker together. See Introduction to .NET and Docker to learn more.

You can run this image as a sidecar container to collect diagnostic information and artifacts from other containers running .NET Core 3.1 or .NET 5 and later.

See Running in Kubernetes or Running in Docker Compose for examples of how to run this image in orchestration environments.

See documentation for how to configure the image and documentation for the web API.

Related Repositories

.NET:

dotnet: .NET
dotnet/monitor: .NET Monitor Tool
dotnet/nightly/sdk: .NET SDK (Preview)
dotnet/nightly/aspnet: ASP.NET Core Runtime (Preview)
dotnet/nightly/runtime: .NET Runtime (Preview)
dotnet/nightly/runtime-deps: .NET Runtime Dependencies (Preview)
dotnet/nightly/monitor/base: .NET Monitor Base (Preview)
dotnet/nightly/aspire-dashboard: .NET Aspire Dashboard (Preview)
dotnet/nightly/yarp: YARP (Yet Another Reverse Proxy) (Preview)
dotnet/samples: .NET Samples

.NET Framework:

dotnet/framework: .NET Framework, ASP.NET and WCF
dotnet/framework/samples: .NET Framework, ASP.NET and WCF Samples

Full Tag Listing

Linux amd64 Tags

Tags	Dockerfile	OS Version
9.0.4, 9.0, 9	Dockerfile	Azure Linux 3.0
8.1.2-ubuntu-chiseled, 8.1-ubuntu-chiseled, 8-ubuntu-chiseled, 8.1.2, 8.1, 8	Dockerfile	Ubuntu 22.04
8.1.2-azurelinux-distroless, 8.1-azurelinux-distroless, 8-azurelinux-distroless	Dockerfile	Azure Linux 3.0

.NET Monitor Preview Tags

Tags	Dockerfile	OS Version
10.0.0-rc.2, 10.0-preview, 10.0-preview, latest	Dockerfile	Azure Linux 3.0
9.1.0-preview.3, 9.1-preview, 9-preview	Dockerfile	Azure Linux 3.0

Linux arm64 Tags

Tags	Dockerfile	OS Version
9.0.4, 9.0, 9	Dockerfile	Azure Linux 3.0
8.1.2-ubuntu-chiseled, 8.1-ubuntu-chiseled, 8-ubuntu-chiseled, 8.1.2, 8.1, 8	Dockerfile	Ubuntu 22.04
8.1.2-azurelinux-distroless, 8.1-azurelinux-distroless, 8-azurelinux-distroless	Dockerfile	Azure Linux 3.0

.NET Monitor Preview Tags

Tags	Dockerfile	OS Version
10.0.0-rc.2, 10.0-preview, 10.0-preview, latest	Dockerfile	Azure Linux 3.0
9.1.0-preview.3, 9.1-preview, 9-preview	Dockerfile	Azure Linux 3.0

Tags not listed in the table above are not supported. See the Supported Tags Policy. See the full list of tags for all supported and unsupported tags.

Support

Lifecycle

Microsoft Support for .NET
Supported Container Platforms Policy
Supported Tags Policy

Image Update Policy

Base Image Updates: Images are re-built within 12 hours of any updates to their base images (e.g. debian:bookworm-slim, windows/nanoserver:ltsc2022, etc.).
.NET Releases: Images are re-built as part of releasing new .NET versions. This includes new major versions, minor versions, and servicing releases.
Critical CVEs: Images are re-built to pick up critical CVE fixes as described by the CVE Update Policy below.
Monthly Re-builds: Images are re-built monthly, typically on the second Tuesday of the month, in order to pick up lower-severity CVE fixes.
Out-Of-Band Updates: Images can sometimes be re-built when out-of-band updates are necessary to address critical issues. If this happens, new fixed version tags will be updated according to the Fixed version tags documentation.

CVE Update Policy

.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:

We detect the image contains a CVE with a CVSS score of "Critical"
AND the CVE is in a package that is added in our Dockerfile layers (meaning the CVE is in a package we explicitly install or any transitive dependencies of those packages)
AND there is a CVE fix for the package available in the affected base image's package repository.

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.

Feedback

File an issue
Contact Microsoft Support

License

Legal Notice: Container License Information
.NET license
Discover licensing for Linux image contents

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!