Apple M1: cpu resource is exhausted

[hanshasselberg]

Nomad version

Output from nomad version: v1.1.0.

Operating system and Environment details

macOS Big Sur with M1 Chip

Issue

Nomad doesn't properly detect the CPU resources I have and claims CPU is exhausted even though there is plenty left. I went back to v1.0.4 which fixed it.

Reproduction steps

Expected Result

Actual Result

Job file (if appropriate)

Nomad Server logs (if appropriate)

Nomad Client logs (if appropriate)

[jk563]

I see the same issue following the Getting Started guide. The initial example.nomad works as expected, but in the "Scale and Update a Job" section when moving to count = 3 running the job fails to place all 3 (it successfully places 2). The plan also indicades it'll fail.

[mikenomitch]

This workaround was mentioned in this issue, but also wanted to mention it here for visibility:

Setting cpu_total_compute in your client config can manually "fix" this until the underlying fingerprinter works properly.