search

docker / for-win

Bug reports for Docker Desktop for Windows
https://www.docker.com/products/docker#/windows
1.85k stars 287 forks source link

Docker windows only "10 cores allocated" on 64 cores wsl2 (72c/144t host) #13730

Open pnthai88 opened 11 months ago

pnthai88 commented 11 months ago

Description

image

I'm trying to get more cores on docker engine at section "Container CPU usage" it only allocated 10 cores My system have 64 cores in WSL2 and 72c/144t on host

Reproduce

Just simple start docker-compose and docker run

Expected behavior

No response

docker version

C:\Users\thai>docker version
Client:
 Cloud integration: v1.0.35+desktop.5
 Version:           24.0.6
 API version:       1.43
 Go version:        go1.20.7
 Git commit:        ed223bc
 Built:             Mon Sep  4 12:32:48 2023
 OS/Arch:           windows/amd64
 Context:           default

Server: Docker Desktop 4.24.0 (122432)
 Engine:
  Version:          24.0.6
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.7
  Git commit:       1a79695
  Built:            Mon Sep  4 12:32:16 2023
  OS/Arch:          linux/amd64
  Experimental:     true
 containerd:
  Version:          1.6.22
  GitCommit:        8165feabfdfe38c65b599c4993d227328c231fca
 runc:
  Version:          1.1.8
  GitCommit:        v1.1.8-0-g82f18fe
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

C:\Users\thai>docker info
Client:
 Version:    24.0.6
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.11.2-desktop.5
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.22.0-desktop.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-compose.exe
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-dev.exe
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.20
    Path:     C:\Program Files\Docker\cli-plugins\docker-extension.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.8
    Path:     C:\Program Files\Docker\cli-plugins\docker-init.exe
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-sbom.exe
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-scan.exe
  scout: Docker Scout (Docker Inc.)
    Version:  v1.0.7
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe

Server:
 Containers: 89
  Running: 88
  Paused: 0
  Stopped: 1
 Images: 32
 Server Version: 24.0.6
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: active
  NodeID: qtlbuvp6hy4uq6lp7pwza0hvi
  Is Manager: true
  ClusterID: ewbvib1qf50lz0lqq6v72vcw0
  Managers: 1
  Nodes: 1
  Default Address Pool: 10.0.0.0/8
  SubnetSize: 24
  Data Path Port: 4789
  Orchestration:
   Task History Retention Limit: 5
  Raft:
   Snapshot Interval: 10000
   Number of Old Snapshots to Retain: 0
   Heartbeat Tick: 1
   Election Tick: 10
  Dispatcher:
   Heartbeat Period: 5 seconds
  CA Configuration:
   Expiry Duration: 3 months
   Force Rotate: 0
  Autolock Managers: false
  Root Rotation In Progress: false
  Node Address: 192.168.65.3
  Manager Addresses:
   192.168.65.3:2377
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 8165feabfdfe38c65b599c4993d227328c231fca
 runc version: v1.1.8-0-g82f18fe
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
 Kernel Version: 5.5.10-microsoft-standard
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 64
 Total Memory: 491.9GiB
 Name: docker-desktop
 ID: a3b0483e-5160-4438-ac10-a9b2e224b20d
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Experimental: true
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: daemon is not using the default seccomp profile

Diagnostics ID

B56C46C2-4ABC-42DB-818A-873B69EEA8F1/20231008082525

Additional Info

No response

ksh117700 commented 11 months ago

good job

fightingsleep commented 11 months ago

Seeing the same thing. My .wslconfig is allocating 15 processors, but in Docker Desktop it only shows "1000% (10 cores allocated)"

igorPiNetwork commented 11 months ago

i have the same problem, 20 physical xeon cores, 40 threads. But Docker allocated only 10 Cores. I need speed-help. write me plz on geist.i@web.de

4-FLOSS-Free-Libre-Open-Source-Software commented 11 months ago

Seeing the same thing. My .wslconfig is allocating 15 processors, but in Docker Desktop it only shows "1000% (10 cores allocated)"

Same for me, with .wslconfig

[wsl2]
processors=15

docker version Docker Desktop 4.24.2 (124339) docker info 

Client:
 Version:    24.0.6
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.11.2-desktop.5
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.22.0-desktop.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-compose.exe
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-dev.exe
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.20
    Path:     C:\Program Files\Docker\cli-plugins\docker-extension.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.8
    Path:     C:\Program Files\Docker\cli-plugins\docker-init.exe
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-sbom.exe
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-scan.exe
  scout: Docker Scout (Docker Inc.)
    Version:  v1.0.7
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe
Kernel Version: 5.15.123.1-microsoft-standard-WSL2
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 15

Docker allocated only 10 Cores

igorPiNetwork commented 11 months ago

i have sent a message with diagnostic id to Docker Support. As soon as I have new information, I'll post everything here

welldone43 commented 11 months ago

Same issue here

igorPiNetwork commented 11 months ago

Thank you for reaching out to us!

We’ve checked and confirmed you currently have a personal/free subscription with Docker.

This support channel is reserved for customers currently subscribed to a Docker Hub Pro, Team. Business Plan or customers who are having issues with their account, billing, or other services associated with Docker Hub.

For users currently on a Docker Hub Free plan, architectural design guidance, or general inquiries, here are some resources that are available to you:

Docker Community Forums: https://forums.docker.com/

Third-Party Communities: http://www.docker.com/community/

Docker Documentation: https://docs.docker.com/

welldone43 commented 10 months ago

Hi Igor,

thanks for looking into the issue of having only 10 cores.

Your are right, my GitHub account points only to a free subscription as that is my private account. I work with a Pro license, but communicate on GitHub only with the private account and hence you can not see it.

igorPiNetwork commented 10 months ago

Hi wdoerr, can you ask please the docker support how to solve this problem with 10 cores? I cant because have only private use.

ztolley commented 9 months ago

I have Docker with a pro licence and I have this problem so can you tell Me why on a 32c/64t machine Docker Desktop reports 10 cores available?

reitowo commented 9 months ago

Same here

ejrobinson commented 8 months ago

Still an issue, however on my end it looks like it might just be a UI issue, behind the scenes, docker seems to be hitting all 24 cores I have.