One correction, “source /etc/platform/openrc|grep Platform”, should be
“source /etc/platform/openrc; system host-cpu-list controller-0|grep Platform”
If you get an error “Can not lock an active controller” then you will need to run a system host-swact command first before you can lock the host. Repeat the
same steps for the other controller.
Tee
From: Ngo, Tee
Sent: April-15-20 12:21 PM
To: Sten Gruener; starlingx-discuss@lists.starlingx.io
Subject: RE: [Starlingx-discuss] CPU configuration for dockerd and nproc
Hi,
You must have deployed an All-in-one. The value reflects the number of cores reserved for platform services “source /etc/platform/openrc|grep Platform”. You
can allocate more cores to platform using system host-cpu-modify command. A host lock/unlock will be required.
Tee
From: Sten Gruener [mailto:stasik@stasik.com]
Sent: April-15-20 12:12 PM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] CPU configuration for dockerd and nproc
Dear community,
we have got starlingx running on bare metal and experience an issue that docker demon claims only 4 cpus out of 32.
"docker info" output contains
CPUs: 4
"nproc" also returns 4
"nproc --all" returns 32 as expected
/usr/lib/systemd/system/docker.service contains
LimitNPROC=infinity
LimitCORE=infinity
Where are these limit of 4 set and how can I change them?
BR
Sten