There is no limit to the container's free, and I still see the memory size of the host, so I feel I need to increase the LXCFS to implement it
- Dominant language
- Go
- Stars
- 2.3k
- Forks
- 303
- PR merge metrics
- No merged PRs in 30d
Description
After running debug, this is still the case, there is no limit, see the container resource visibility is still the host
```
bash-5.0# free -m
total used free shared buff/cache available
Mem: 7820 4423 712 0 2685 3053
Swap: 0 0 0
bash-5.0# exit
exit
[root@master ~]# free -m
total used free shared buff/cache available
Mem: 7820 4012 1006 45 2802 3347
Swap: 0 0 0
```
Remember that there is a project called LXCFS that can achieve the visibility of resources, you can see the visibility of container resources, the author here can be optimized, I don't know if I am right, I hope to get correction
Contributor guide
No contributing guide indexed for this repository
Research direction
No source file, test, or entry point is identified in the report. Start by reviewing the referenced LXCFS resource-visibility approach alongside kubectl-debug's container behavior; done means the container reports its configured memory limit rather than the host's memory size.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100