Skip to content

Known issue with container CPU and memory limits in February release #889

@mthalman

Description

@mthalman

Today's February release has a known issue that causes the newly announced CPU and memory limits feature to not work correctly. This affects those users that make use of Docker's --cpus or -m switches and are running a .NET Framework 4.8 container on a Windows Server 2019 or 2022 host machine with process isolation. It effectively behaves as though this container CPU and memory limits functionality is not enabled. This is an active issue that we're currently investigating. We'll make further updates to this issue when we have more information.

If you're blocked by this issue and need to fall back to last month's version of the image, you can do so by using the following tags:

  • Windows Server Core 2019: 4.8-20220111-windowsservercore-ltsc2019
  • Windows Server Core 2022: 4.8-20220111-windowsservercore-ltsc2022

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions