Hi folks - My colleagues and I are running a few bosh-lite VM's to do some manifest validation before passing changes on to a "real" microbosh environment. Therefore, we have a few central bosh-lites running (one for each set of environments) that run multiple deployments.

Currently, we're running into a problem where the Garden containers consume so much memory (running in a 32GB bosh-lite btw) that other Garden containers become unable to consume memory, and we have to restart the VM.

In researching this problem, I was able to query Garden in bosh-lite (logged in as vcap) with the following command to get the memory limits - according to Garden, this limit is not being set - even if I specifically set it in the resource pools in any of the manifests:

The command:
for i in $(curl -s http://127.0.0.1:7777/containers | jq -r '.handles[]'); do echo $(curl -s "http://127.0.0.1:7777/containers/$i/limits/memory" | jq -r '.limit_in_bytes'); done;

The output:
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000
9223372036854772000

Can someone confirm that this is a bug, and if so, where should I report it?

Cheers,
Jeremy

This is expected behavior currently. We dont do any kind of limiting in
bosh-lite. Feel free to file an issue on cloudfoundry/bosh-lite and specify
what kind of type of limits we should make available via cloud_properties
(e.g. ram).