Fix cgroupv2 mem usage calculation to match docker cli #3370
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
"cache" memory stat no longer exists in cgroupv2.
docker cli subtracts "inactive_file" for the overall mem usage
calculation, so do the same for cgroupv2.
closes #3323
for reference also see moby/moby#40727
Summary
Testing
Agent code was instrumented to log the exact mem usage that it is sending to cloudwatch. This was then manually compared to what docker cli outputs before and after this change.
Note in the logging below that the mem usage "AFTER" this change more accurately matches the docker cli value of 51.85 MiB
also see #3323
New tests cover the changes: no
Description for the changelog
Bugfix: Fix cgroupv2 mem usage calculation to match docker cli
Licensing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.