dotnet-docker
dotnet-docker copied to clipboard
Docker images for .NET and the .NET Tools.
### Describe the Problem Noble images are failing to build on our CI machines due to https://bugs.launchpad.net/ubuntu/+source/tar/+bug/2059734. ### Describe the Solution Continue investigating the issue above and add Noble arm32...
Alpine floating tags are moving to 3.19 with https://github.com/dotnet/dotnet-docker/issues/5093. Our [supported tags documentation](https://github.com/dotnet/dotnet-docker/issues/5093) says that after 3 months of the floating tags being moved, we will remove the old Alpine...
We should explore the possibility of using [Marinara](https://github.com/microsoft/marinara) for the production of our distroless Mariner images. This tool is intended to simplify the installation of additional packages on top of...
The .NET Docker infrastructure for automatically rebuilding images in response to base image updates is not enabled for Windows images on the .NET Docker main branch. My understanding is that...
Now that [Mariner images are publicly supported](https://github.com/dotnet/dotnet-docker/discussions/5022), Mariner should be covered as an OS option in the [vulnerability reporting doc](https://github.com/dotnet/dotnet-docker/blob/main/documentation/vulnerability-reporting.md). This will help guide people with Mariner-specific commands and resources.
Our Dockerfiles are authored to execute multi-statement PowerShell scripts with statement semi-colon separators. This allows for multiple statements to be executed in a single command line. The issue with this...
Signing a container image involves using a digital signature that includes information about the image, such as its hash value, and is created using a private key. The consumer can...
There's a gap in the scenarios covered by the [Container Vulnerability Workflow doc](https://github.com/dotnet/dotnet-docker/blob/main/documentation/vulnerability-reporting.md). If the container image contains a .NET app where that app references NuGet packages which are vulnerable,...
There was an [issue](https://github.com/dotnet/dotnet-docker/issues/4537) that required the tests to [pin to an older version of syft](https://github.com/dotnet/dotnet-docker/pull/4541). The solution to that was discovered that will allow us to now go back...
Instructions here: https://github.com/dotnet/arcade-services/tree/main/src/Microsoft.DncEng.SecretManager#onboarding-a-new-repo