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]: Debian container images upgraded to Debian 12 (Bookworm) #35953

Closed
2 of 3 tasks
mthalman opened this issue Jun 26, 2023 · 0 comments · Fixed by #36238
Closed
2 of 3 tasks

[Breaking change]: Debian container images upgraded to Debian 12 (Bookworm) #35953

mthalman opened this issue Jun 26, 2023 · 0 comments · Fixed by #36238
Assignees
Labels
binary incompatible Existing binaries may encounter a breaking change in behavior. breaking-change Indicates a .NET Core breaking change doc-idea Indicates issues that are suggestions for new topics [org][type][category] Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Identifies that an issue has been imported into Quest.

Comments

@mthalman
Copy link
Member

mthalman commented Jun 26, 2023

Description

The default Linux distro for .NET container images is Debian. In .NET 8, the Debian version has been upgraded to Debian 12 (Bookworm). This new version of Debian may have changes in it that break your application as is the case with any OS version upgrade. This is a result of upgraded package versions. The most notable change is the upgrade of Open SSL from 1.1 to 3.0.

Version

.NET 8 Preview 1

Previous behavior

In .NET 6 and 7, the default Debian version was Debian 11 (Bullseye).

Notable package versions:

  • libicu: 67
  • libssl: 1.1

New behavior

In .NET 8, the default Debian version is Debian 12 (Bookworm).

Notable package versions:

  • libicu: 72
  • libssl: 3

Type of breaking change

  • Binary incompatible: Existing binaries may 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 may require source changes to compile successfully.
  • Behavioral change: Existing binaries may behave differently at run time.

Reason for change

According to the container support policy, with each version of .NET, the latest stable version of Debian is targeted as the default version.

Recommended action

Please review Debian 12's release notes for more details.

Feature area

Deployment

Affected APIs

No response


Associated WorkItem - 118221

@mthalman mthalman 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 Jun 26, 2023
@dotnet-bot dotnet-bot added ⌚ Not Triaged Not triaged binary incompatible Existing binaries may encounter a breaking change in behavior. labels Jun 26, 2023
@gewarren gewarren added 🗺️ reQUEST Triggers an issue to be imported into Quest. and removed ⌚ Not Triaged Not triaged labels Jun 27, 2023
@github-actions github-actions bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Jun 28, 2023
@ghost ghost added in-pr This issue will be closed (fixed) by an active pull request. and removed in-pr This issue will be closed (fixed) by an active pull request. labels Jul 12, 2023
@ghost ghost removed the in-pr This issue will be closed (fixed) by an active pull request. label Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
binary incompatible Existing binaries may encounter a breaking change in behavior. breaking-change Indicates a .NET Core breaking change doc-idea Indicates issues that are suggestions for new topics [org][type][category] 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