automaxprocs icon indicating copy to clipboard operation
automaxprocs copied to clipboard

Automatically set GOMAXPROCS to match Linux container CPU quota.

Results 19 automaxprocs issues
Sort by recently updated
recently updated
newest added

**version** v1.5.3 **error info** msg="failed to set GOMAXPROCS: path "/kubepods.slice/kubepods-pod3f8b57a9_829a_4d47_b220_b830da173956.slice/cri-containerd-2b7a54862ac13ec3bf45d691f6e900ba67b27ca3718dab124f6d04e1644ee53e.scope" is not a descendant of mount point root "/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod497e810a_3a2e_49d6_a6a3_ca9b49062993.slice/cri-containerd-f3ee784b971d2e8e2bff1714496b5c813a9f6dc0e726530b004a4a1a01bc470e.scope" and cannot be exposed from "/sys/fs/cgroup/systemd""

How does it work? How does it automatically set the value of GOMAXPROCS based on the cgroup? Where does it read the cpu resources for the cgroup setting?

hi, i have the case with quota 2.9 so i think the proper way is to set max procs to 3, instead of 2

Unlike Kubernetes, ECS only allows you to apply a CPU quota at the task (pod) level. Containers in the task are always unbounded. For example, when `cpu: 1024` (1 vCPU)...

This releases v1.6.0.

Would it be possible to tag a new release in the near future to get the changes from #79?

We've longed moved away to go.mod and install using glide is no longer supported. Remove glide.yaml file to clean up unused files.

And drop the older Go versions in test matrix.