We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Many container engines are today built on runC. A few notable examples:
Wonder if we could make ctop work with runC? It would have to be on the host that's running runC containers but that's probably not too much to ask.
WDYT?
The text was updated successfully, but these errors were encountered:
@williammartin
Sorry, something went wrong.
runC support is certainly possible, as libcontainer does export the Stats() method (for Linux containers only)
Stats()
An initial runc connector implementation is available on the runc branch.
Running via docker:
docker run --rm -ti --name ctop \ -v /run/runc:/run/runc \ -v /sys:/sys \ --pid=host \ quay.io/vektorlab/ctop:runc --connector runc
Containers created via docker will be missing names and some other metadata; however stat collection and all other functionality is available.
merged in latest release
No branches or pull requests
Many container engines are today built on runC. A few notable examples:
Wonder if we could make ctop work with runC? It would have to be on the host that's running runC containers but that's probably not too much to ask.
WDYT?
The text was updated successfully, but these errors were encountered: