Curious, has anyone seen a buildpack with a manifest file work in one segment, but that same app and manifest file not work in an isolation segment?  What happens is you run cf push app name, the app fails at the droplet stage, although you can still manually start the app. Do note that the underlying resources are identical, diego cells, and the buildpack is NGINX.  Adding more memory to the manifest does solve the issue, 1GB to 2 GB, but curious why more memory would be needed between two different segments.  Nothing here stands out https://docs.cloudfoundry.org/adminguide/isolation-segment-index.html. other than networking.  I am in discussions with Pivotal but wanted to see if anyone here had issues like this elsewhere?  It's just a weird problem to say the least.

Sorry about that, this would be the log

[STG/0] [OUT] [31;1m**ERROR** [0m Could not validate nginx.conf: Error copying nginx.conf: write  /tmp/conf879997043/public/privacy/cross-border-privacy-policy/js/jquery-ui.js: cannot allocate memory

 [STG/0] [ERR] Failed to compile droplet: Failed to run all supply scripts: exit status 14

 [STG/0] [OUT] Exit status 223

Cannot allocate memory, is a bit vague I guess you can say.

 

Not that I can see, although we also do frequent "repaves" and we also somewhat recently did an upgrade to a newer version.  I'd like to think if it was a Diego cell it would have been destroyed and or rebuilt at one of those junctures?