Debian 11 images now available #3695
Replies: 5 comments
-
| 
         Hi, due to this inconsistency for debian 11 image tags, the following Dockerfile would no longer work for across 3.1 and 5.0 # [Choice] .NET version: 5.0, 3.1
ARG VARIANT="3.1"
FROM mcr.microsoft.com/dotnet/sdk:${VARIANT}-bullseyeNote: this is not the case with ubuntu focal, as both 3.1-focal and 5.0-focal are available  | 
  
Beta Was this translation helpful? Give feedback.
-
        
 Yes, this is intentional. This change is only for the   | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Maybe a bit off-topic, but is bullseye the default for .NET 6?  | 
  
Beta Was this translation helpful? Give feedback.
-
        
 @ThorstenHans - Yes, it is.  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Is the 372268-GNU Bash Privilege Escalation Vulnerability for Debian still present in the Debian 11 image? CVE-2019-18276Saw it still popping in the Qualys scan for Azure Container Registry.  | 
  
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Debian 11 images now available
Debian 11 (Bullseye) container images have been released for .NET Core 3.1 & 5.0 (they were already previously available for .NET 6 previews). To consume this new version of Debian, you'll need to use one of the
<dotnet-version>-bullseyetags. No change is being made to the floating3.1and5.0tags; these will continue to reference Debian 10 (Buster).Details
The floating
3.1and5.0tags are not being moved to reference Debian 11 since that would be a breaking change. So in order to consume this new version of Debian, you'll need to explicitly target it with the tag name:3.1-bullseye,5.0-bullseye. For other variations of these tag names for Debian 11, see the full list of documented tags on Docker Hub:Beta Was this translation helpful? Give feedback.
All reactions