-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cat /proc/stat
shows a bunch of zeros
#9967
Comments
/proc/stat
shows a bunch of zeroscat /proc/stat
shows a bunch of zeros
This is a known deficiency: gvisor/pkg/sentry/fsimpl/proc/tasks_files.go Lines 187 to 195 in b09abbe
Good way to investigate this would be to run |
Oh, that's an excellent idea! I verified that there is a syscall to open |
Do you know how difficult this functionality would be to implement? Would the implementation of overall CPU stats be to maintain an I'm not sure how to get per-core aggregate information... |
Description
When I
cat /proc/stat
in gvisor, I see a bunch of zeros:As such, I think tools like
htop
don't work (the CPU usage shown is just always zero). My goal is mostly to be able to runhtop
within a runsc container.Steps to reproduce
You will see a bunch of zeros. Alternatively, run
htop
within a runsc container; the CPU usage will be zero everywhere.runsc version
No response
docker version (if using docker)
Client: Docker Engine - Community Version: 24.0.7 API version: 1.43 Go version: go1.20.10 Git commit: afdd53b Built: Thu Oct 26 09:08:01 2023 OS/Arch: linux/amd64 Context: default Server: Docker Engine - Community Engine: Version: 24.0.7 API version: 1.43 (minimum version 1.12) Go version: go1.20.10 Git commit: 311b9ff Built: Thu Oct 26 09:08:01 2023 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.26 GitCommit: 3dd1e886e55dd695541fdcd67420c2888645a495 runc: Version: 1.1.10 GitCommit: v1.1.10-0-g18a0cb0 docker-init: Version: 0.19.0 GitCommit: de40ad0
uname
Linux ip-10-1-5-239 5.15.0-1048-aws #53~20.04.1-Ubuntu SMP Wed Oct 4 16:44:20 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
kubectl (if using Kubernetes)
No response
repo state (if built from source)
release-20240122.0-27-gac416763d
runsc debug logs (if available)
No response
The text was updated successfully, but these errors were encountered: