Re: java buildpack debugging - how to pass memory value without manifest file ...
That worked. Thanks a lot Dan.toggle quoted messageShow quoted text
On Friday, 17 July 2015 6:38 PM, Daniel Mikusa <dmikusa(a)pivotal.io> wrote:
On Fri, Jul 17, 2015 at 8:48 AM, Vishwanath V <thelinuxguyis(a)yahoo.co.in> wrote:
I am trying to customize the java build-pack with oracle jre.
however, when trying to debug it locally , using the below commands :
JBP_LOG_LEVEL=DEBUG ../java-buildpack/bin/detect app/
JBP_LOG_LEVEL=DEBUG ../java-buildpack/bin/compile app/ tmp/
I am getting the below error :
[DownloadCache] DEBUG Validated content size 63819486 is 63819486
Expanding Oracle JRE to .java-buildpack/oracle_jre (1.6s)
[Droplet] DEBUG Resources /home/tux/debug-javabuildpack/java-buildpack/resources/oracle_jre found
[DownloadCache] DEBUG Validated content size 2406200 is 2406200
-totMemory must be specified
[Buildpack] ERROR Compile failed with exception RuntimeError
Question: How can I pass Memory value without a manifest.yml file ?
Set an environment variable called `MEMORY_LIMIT`. When the build pack runs it'll look at that env variable to see the max memory assigned to the container.
cf-dev mailing list