Bug #8096: Core count can cause "numerical result out of range" error due to off-by-one error - Docker - Foreman

Actions

Copy link

Bug #8096

closed

Core count can cause "numerical result out of range" error due to off-by-one error

Added by Dominic Cleal almost 10 years ago. Updated almost 10 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman-docker/pull/38

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

On a single core VM, I tried to create a container when specifying a core count of 1, but get the following error when starting the container:

Error - Cannot start container 54981773be64869adb7bac933a15df8245bc4182fce2c299133357eebce11fa8: write /sys/fs/cgroup/cpuset/docker-54981773be64869adb7bac933a15df8245bc4182fce2c299133357eebce11fa8/cpuset.cpus: numerical result out of range

cgroup cpusets are counted from zero IIRC, so if core count is meant to equate to a cpuset, it should probably have 1 subtracted from the number selected.

If I change the form to start from zero, then I can select zero CPUs and the container seems to start.