*: fix InContainer check for cgroup v2

[D3Hunter]

What problem does this PR solve?

Issue Number: close #51668

Problem Summary:

What changed and how does it work?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
  before

[2024/03/11 09:54:43.469 +00:00] [INFO] [meminfo.go:196] ["use physical memory hook"] [cgroupMemorySize=68719476736] [physicalMemorySize=67536244736]

after

[2024/03/11 12:36:07.807 +00:00] [INFO] [meminfo.go:179] ["use cgroup memory hook because TiDB is in the container"]
[2024/03/11 12:36:07.808 +00:00] [INFO] [printer.go:47] ["Welcome to TiDB."] ["Release Version"=v7.5.0-incontainer2gcp] [Edition=Community] ["Git Commit Hash"=6bf81524079e80de19be644fc0ca43e1f98e0019] ["Git Branch"=heads/refs/tags/v7.5.0-incontainer2gcp] ["UTC Build Time"="2024-03-11 12:26:20"] [GoVersion=go1.21.6] ["Race Enabled"=false] ["Check Table Before Drop"=false]

• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[tiprow]

Hi @D3Hunter. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[purelind]

/test mysql-test

[tiprow]

@purelind: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test mysql-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[codecov]

Codecov Report

Merging #51669 (38d64d7) into master (2b63184) will increase coverage by 2.0229%.
Report is 7 commits behind head on master.
The diff coverage is 0.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #51669        +/-   ##
================================================
+ Coverage   70.7224%   72.7454%   +2.0229%     
================================================
  Files          1473       1473                
  Lines        437089     437816       +727     
================================================
+ Hits         309120     318491      +9371     
+ Misses       108602      99270      -9332     
- Partials      19367      20055       +688     

Flag	Coverage Δ
integration	48.7440% <0.0000%> (?)
unit	70.4696% <0.0000%> (-0.0520%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	51.1463% <ø> (+5.2918%)	⬆️

[hawkingrei]

You need to add tests for it.

[D3Hunter]

manually testing

[D3Hunter]

updated in pr desc

[hawkingrei]

/ok-to-test

[D3Hunter]

/retest

[D3Hunter]

/hold

i will test it again manually, as the logic changed

[D3Hunter]

test again

2024-03-12 12:05:22 (UTC+08:00)TiDB tc-tidb-0.tc-tidb-peer.gsort-import-gcp-tps-7470320-1-17.svc:4000[meminfo.go:179] ["use cgroup memory hook because TiDB is in the container"]

[D3Hunter]

/unhold

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Defined2014, hawkingrei

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Defined2014,hawkingrei]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-03-12 03:07:01.755912369 +0000 UTC m=+741248.778158758: ☑️ agreed by Defined2014.
• 2024-03-12 04:10:13.366019338 +0000 UTC m=+745040.388265723: ☑️ agreed by hawkingrei.