Skip to content
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

[Breaking change]: .NET 9 container images no longer install zlib #42136

Closed
1 of 3 tasks
lbussell opened this issue Aug 13, 2024 · 0 comments · Fixed by #42383
Closed
1 of 3 tasks

[Breaking change]: .NET 9 container images no longer install zlib #42136

lbussell opened this issue Aug 13, 2024 · 0 comments · Fixed by #42383
Assignees
Labels
breaking-change Indicates a .NET Core breaking change doc-idea Indicates issues that are suggestions for new topics [org][type][category] in-pr This issue will be closed (fixed) by an active pull request. Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Identifies that an issue has been imported into Quest.

Comments

@lbussell
Copy link

lbussell commented Aug 13, 2024

Description

.NET 9 container images no longer install zlib since it is no longer a dependency of the .NET Runtime.

Version

.NET 9 Preview 7

Previous behavior

In previous .NET versions, .NET container images installed the latest version of the zlib package from the Linux base image package repositories.

New behavior

.NET 9 container images no longer install zlib, and no longer update zlib in images where it is already installed from the base image.

Type of breaking change

  • Binary incompatible: Existing binaries might encounter a breaking change in behavior, such as failure to load or execute, and if so, require recompilation.
  • Source incompatible: When recompiled using the new SDK or component or to target the new runtime, existing source code might require source changes to compile successfully.
  • Behavioral change: Existing binaries might behave differently at run time.

Reason for change

In .NET 9, the Runtime contains a statically linked version of zlib-ng. As a result, the .NET Runtime no longer has a package dependency on zlib. In order to reduce .NET container image sizes, .NET 9 container images no longer install zlib, and no longer update zlib in images where it is already installed from the base Linux image.

Recommended action

For most scenarios, no action is required. If your containerized .NET app has a direct package dependency on zlib, you should manually install it in your Dockerfile using the package manager.

Feature area

Containers

Affected APIs

No response


Associated WorkItem - 297232

@lbussell lbussell added doc-idea Indicates issues that are suggestions for new topics [org][type][category] breaking-change Indicates a .NET Core breaking change Pri1 High priority, do before Pri2 and Pri3 labels Aug 13, 2024
@gewarren gewarren added the 🗺️ reQUEST Triggers an issue to be imported into Quest. label Aug 13, 2024
@sequestor sequestor bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Aug 14, 2024
@dotnet-policy-service dotnet-policy-service bot added the in-pr This issue will be closed (fixed) by an active pull request. label Aug 29, 2024
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in dotnet/docs August 2024 Sprint Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change Indicates a .NET Core breaking change doc-idea Indicates issues that are suggestions for new topics [org][type][category] in-pr This issue will be closed (fixed) by an active pull request. Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Identifies that an issue has been imported into Quest.
Projects
No open projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

3 participants
@gewarren @lbussell and others