Thanks for the response Eric. It was very helpful. One last question. Any thoughts on what would be the best way to monitor free ephemeral disk space in my overcommitted situation? If

Thanks JT for your answer. Based on our experience, one of the best practice to share is that it's a good idea to set all the below four environment variables: http_proxy, HTTP_PROXY, https_proxy,

We have a workaround in place for the above issue (hack code to disable connection pooling) and it seems to have addressed this problem until we can get a better fix. We've also just filed a new bug

Thanks for the details. I deployed diego-docker-cache-release and I could run private docker images now. One note however. I had to modify the **property-overrides.yml *to add the IP:<port> of the

What do you use for your edge load balancer? You could try to set up your edge load balancer to strip x_forwarded_for sent in the request and set it again before forwarding on. In that way, I believe

In the Docker image case, the filesystem layer specific to the container is also deleted immediately when the container stops running (this is the same for buildpack based apps on Diego/Garden). Lower

Gist of diff: https://gist.github.com/simonjohansson/847e972f1459ea4cd65e Gist of debug output: https://gist.github.com/simonjohansson/3324b08fc42e5ac7105a Since it's quite hard to read in the

Hiya! Im looking into an issue where the x_forwarded_for have different values depending on what you are using to hit it with. With curl, w3m, lynx x_forwarded_for gets set to "sourceIP,

warden/DEAs keeps container file systems for a configured amount of time, something like 1 hr before removing the containers, i believe with standard removal tools. diego cells and garden removes

use the syslog nozzle to get system component logs and send them to your syslog server of choice. https://github.com/cloudfoundry-community/firehose-to-syslog wrote: -- Thank you, James Bayer

what is your logging and metrics tool? does it have an api? the loggregator nozzle's are the go-forward approach to tapping into logs and metrics in the entire cf system and sending them

i don't believe the current docker support includes support for private docker images on a docker registry that require authentication. that does not seem to be listed in the diego docker docs [1]

there is no standard notification mechanism built into cf today for this kind of information. as an administrator, you could possibly potentially build and deploy a loggregator firehose nozzle that

here is some guidance on how to check for available entropy on a linux host [1]. i'm not sure if the bosh agent, DEA or diego cell captures this metric or not. but we should certainly look into it.

I've seen this happen to a good number of apps running on PWS, so it's something you can encounter when running CF on AWS as well. What usually happens is that the application takes significantly

ahmadferdous(a)gmail.com> wrote: How are you trying to connect to App1 from App2? If you access App2's URL, it should work? i.e. app-2.your-cf-domain.com For inbound traffic, the restriction is

i use cf cli 6.12.2 (so the latest) -- View this message in context: http://cf-dev.70369.x6.nabble.com/no-more-stdout-in-app-files-since-upgrade-to-214-tp1197p1275.html Sent from the CF Dev mailing

Hi, I have a few questions regarding the way data is removed when an application is removed and its corresponding warden container is destroyed. As the Cloud Foundry instance my company is using may

same query for the component logs -- View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-More-reliable-way-to-collect-user-application-logs-tp1214p1273.html Sent from the CF Dev

Go for it and let's see if we can document this issue afterwards with some logs for other people. daniel.jones(a)engineerbetter.com> wrote: -- Mit freundlichen Grüßen Johannes Hiemer