cloudfoundry / cloudfoundry/bpm-release
System memory information is incorrect in BPM containers when using the docker cpi
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 33
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
We use lxcfs mounts through the docker cpi to ensure the containers and processes don't attempt to take more memory than they should.
Turns out, when bpm creates containers for processes, because it does not explicitly mount the information, it defaults back to the host vm information. It'd be great if processes managed by bpm in docker deployed envs maintained the memory limits that were provided to it. I can imagine this might also extend to other type of information that bpm could/should explicitly mount into the containers it is creating.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the docker CPI reference in src/bosh-docker-cpi/vm/factory.go, then locate where BPM creates process containers and how container mounts are configured. Verify how lxcfs mounts are passed through and confirm that processes see their configured memory limits rather than host VM information; investigate other system information only if the existing container setup points there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100