Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removed Reference to buildpack-deps in SDK #1928

Closed
mthalman opened this issue May 16, 2020 · 0 comments
Closed

Removed Reference to buildpack-deps in SDK #1928

mthalman opened this issue May 16, 2020 · 0 comments

Comments

@mthalman
Copy link
Member

Removed Reference to buildpack-deps in SDK

With the release of .NET 5.0 Preview 3, the SDK Docker images for Ubuntu and Debian have been updated to longer reference buildpack-deps as their base image. This is considered a breaking change because any dependencies that existed on that base image may potentially be affected.

Details

Instead of using buildpack-deps as the base image, these SDK images now reference the aspnet images. This change was made in order to provide more layer sharing amongst the set of .NET Docker images and to help reduce the security surface area. See #1814 for more details.

To compensate for the loss of certain packages that were contained in the buildpack-deps base image, the following packages have been explicitly added to the SDK images:

  • curl
  • git
  • wget

The following tags are affected by this change:

  • mcr.microsoft.com/dotnet/core/sdk:5.0
  • mcr.microsoft.com/dotnet/core/sdk:5.0-buster
  • mcr.microsoft.com/dotnet/core/sdk:5.0-buster-arm64v8
  • mcr.microsoft.com/dotnet/core/sdk:5.0-buster-arm32v7
  • mcr.microsoft.com/dotnet/core/sdk:5.0-focal
  • mcr.microsoft.com/dotnet/core/sdk:5.0-focal-arm64v8
  • mcr.microsoft.com/dotnet/core/sdk:5.0-focal-arm32v7
@dotnet dotnet locked and limited conversation to collaborators Apr 13, 2022
@mthalman mthalman converted this issue into discussion #3666 Apr 13, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

2 participants