-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Description
Description
Previously I had a Windows Server 2019 and I could start hundreds of containers without any issue. Now I'm trying to renew my environment with a Windows Server 2022 Datacenter.
I have 3 copies of docker-compose.ymls. Each has a exposed port as follows:
version: '3.8'
services:
web:
image: "mcr.microsoft.com/windows/nanoserver:ltsc2022"
ports:
- "4604:80"
command: "ping 4.2.2.4 -t"
The exposed ports are different on each yml so there is no conflict.
First container starts, Second container start but when staring the THIRD container, the Host Network Service (HNS) comes up in TaskManager, taking 20-30% of CPU and container stuck on starting and nothing happens after this.
I tried several scenarios to reach the simplest way to reproduce this error. The key point is exposing ports on containers. Without exposing ports I can start multiple containers.
What is the difference between networking defaults in Windows Server 2019 and 2022?
Should I start some windows services on 2022?
Steps To Reproduce
No response
Compose Version
No response
Docker Environment
No response
Anything else?
No response
