Comments (7)
Any updates on this, I as well am hitting this same issue
from automaxprocs.
I just verified that #44 fixes the problem.
from automaxprocs.
More information. I have a shell inside the running container. Just not sure what I can do with this information.
# cat /proc/self/cgroup
0::/
# cat /proc/self/mountinfo
1065 962 0:328 / / rw,relatime master:245 - overlay overlay rw,lowerdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/53/fs:/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/52/fs:/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/51/fs,upperdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/55/fs,workdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/55/work
1066 1065 0:330 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
1067 1065 0:331 / /dev rw,nosuid - tmpfs tmpfs rw,size=65536k,mode=755
1068 1067 0:332 / /dev/pts rw,nosuid,noexec,relatime - devpts devpts rw,gid=5,mode=620,ptmxmode=666
1069 1067 0:321 / /dev/mqueue rw,nosuid,nodev,noexec,relatime - mqueue mqueue rw
1070 1065 0:152 / /sys ro,nosuid,nodev,noexec,relatime - sysfs sysfs ro
1071 1070 0:30 / /sys/fs/cgroup ro,nosuid,nodev,noexec,relatime - cgroup2 cgroup rw
1072 1065 254:1 /docker/volumes/2682bff96335d7b90731910f0ca3a21b656691f7a8bd8dcf077be5b29e08b53a/_data/lib/kubelet/pods/9e244aa4-b0e9-40bc-b5ac-f1d5606d99cb/etc-hosts /etc/hosts rw,relatime - ext4 /dev/vda1 rw
1073 1067 254:1 /docker/volumes/2682bff96335d7b90731910f0ca3a21b656691f7a8bd8dcf077be5b29e08b53a/_data/lib/kubelet/pods/9e244aa4-b0e9-40bc-b5ac-f1d5606d99cb/containers/sales-api/9e48480f /dev/termination-log rw,relatime - ext4 /dev/vda1 rw
1074 1065 254:1 /docker/volumes/2682bff96335d7b90731910f0ca3a21b656691f7a8bd8dcf077be5b29e08b53a/_data/lib/containerd/io.containerd.grpc.v1.cri/sandboxes/2663843aea5341800696094fc9b10adc8b4190ee93414c3a1a4caea5d7d6f286/hostname /etc/hostname rw,relatime - ext4 /dev/vda1 rw
1075 1065 254:1 /docker/volumes/2682bff96335d7b90731910f0ca3a21b656691f7a8bd8dcf077be5b29e08b53a/_data/lib/containerd/io.containerd.grpc.v1.cri/sandboxes/2663843aea5341800696094fc9b10adc8b4190ee93414c3a1a4caea5d7d6f286/resolv.conf /etc/resolv.conf rw,relatime - ext4 /dev/vda1 rw
1076 1067 0:318 / /dev/shm rw,nosuid,nodev,noexec,relatime - tmpfs shm rw,size=65536k
1077 1065 0:317 / /run/secrets/kubernetes.io/serviceaccount ro,relatime - tmpfs tmpfs rw,size=6087028k
963 1066 0:330 /bus /proc/bus ro,nosuid,nodev,noexec,relatime - proc proc rw
964 1066 0:330 /fs /proc/fs ro,nosuid,nodev,noexec,relatime - proc proc rw
965 1066 0:330 /irq /proc/irq ro,nosuid,nodev,noexec,relatime - proc proc rw
966 1066 0:330 /sys /proc/sys ro,nosuid,nodev,noexec,relatime - proc proc rw
967 1066 0:330 /sysrq-trigger /proc/sysrq-trigger ro,nosuid,nodev,noexec,relatime - proc proc rw
968 1066 0:333 / /proc/acpi ro,relatime - tmpfs tmpfs ro
969 1066 0:331 /null /proc/kcore rw,nosuid - tmpfs tmpfs rw,size=65536k,mode=755
970 1066 0:331 /null /proc/keys rw,nosuid - tmpfs tmpfs rw,size=65536k,mode=755
971 1066 0:331 /null /proc/timer_list rw,nosuid - tmpfs tmpfs rw,size=65536k,mode=755
986 1066 0:331 /null /proc/sched_debug rw,nosuid - tmpfs tmpfs rw,size=65536k,mode=755
987 1070 0:334 / /sys/firmware ro,relatime - tmpfs tmpfs ro
from automaxprocs.
I have not received anything :(
from automaxprocs.
IMHO you‘re hitting cgroupv2
behavior on your underlying Docker host (where kind
is running). IIUC, should be fixed by #44
from automaxprocs.
I just tried the new 1.5.0 tagged release which was expected to fix the quota for cgroups2. It's not working :(
CPU quota undefined
@abhinav any ideas?
This fork is working
"github.com/emadolsky/automaxprocs/maxprocs"
from automaxprocs.
Based on discussion in #44 and #49, this looks like it's done.
Thanks for testing @ardan-bkennedy!
from automaxprocs.
Related Issues (20)
- Provide an API to expose the read value without setting GOMAXPROCS HOT 3
- is it not default behavior after version 1.5? HOT 2
- no cgroup mountinfo in /proc/self/mountinfo if shareProcessNamespace=true
- qurying memory quota not work when /proc/self/mountinfo match multiple keywords
- v1.5.0 I am still getting that the CPU Quota is not defined. HOT 8
- What happens if cpu quota on k8s side is less than 1 core? HOT 7
- Support for soft RAM limit? HOT 6
- version 1.5.2 increased CPU consumption HOT 4
- invalid format for MountPoint in WSL2 HOT 3
- Doesn't work on ECS (nested cgroups) HOT 1
- go test -cpu HOT 3
- i don't even know what's going on here send help
- NewMountPointFromLine fails under WSL HOT 2
- Kubernetes VPA not working with fractional quotas HOT 3
- []
- [go.mod] Bump Go version to Go 1.21 HOT 3
- How does it work? How does it automatically set the value of GOMAXPROCS based on the cgroup?
- is not a descendant of mount point root
- pls public the internal/cgroups package
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from automaxprocs.