Warden does not create a bind mount to the network namespace. If you want to find the namespace, locate the pid of the wshd associated with the container and use /proc/${pid}/ns/net as the

Nice demo gif on the readme. Looks v handy!

Thanks for asking this question! Deleting blobs from the Buildpack cache would mean users could avoid having to delete their app, which may be an improvement over the process outlined by Danny

Hi, I've written new plugin to update cloudfoundry/cli to the latest version. https://github.com/tcnksm/cf-plugin-update-cli (You can download it from my own plugin repo,

Danny/John, Would deleting all the blobs in the Buildpack cache help to mitigate

Nice work everyone!

Hi, We (the buildpack team) just found out that stacks version 1.47 had an incomplete fix for applications linked against libmysqlclient.so. The new version 1.48 will contain a complete fix for the

Hi again, Would you consider a PR that adds previous memory & instances to the app usage events? Does this two additional fields make a sense? Regards, Hristo Iliev

Why do I not see linux name spaces for my warden instances? root(a)874c4cea-19ed-41c7-abd2-09eb5851d54d:/var/vcap/data/warden/depot# ip netns list <-- note that the output was

I don't have any show stopping cases. But, my 2 main concerns are: * Conceptually speaking if the CATS are for all will making them part of capi hinder other teams from contributing to it? * Having

We had a series of meetings to figure out a good path for CATs that ranged from multiple teams to smaller groups. We met most recently to address concerns that include the following: • Workflow and

Just a heads up, while the community is committed to helping people use CF, people here are essentially volunteering their time and hence cannot respond differently to urgent or blocking

I agree with Michael. I think the CATs and Smoke tests should be in their own release(s). Mike michael.fraenkel(a)gmail.com> wrote:

The Services PMC accepts App-Autoscaling into incubation. Thank you to IBM for the contribution, and to Fujitsu and SAP for the commitment to assist in its maintenance and

Hi Will, Thanks your reply, hope can get response from Garden-Linux soon. Thanks, Sam

CVE-2016-2165 - Loggregator Request URL Paths Severity Medium Vendor Cloud Foundry Foundation Versions Affected - cf-release v231 and lower Description The Loggregator Traffic Controller

CVE-2016-0781 UAA Persistent XSS VulnerabilitySeverity Low Vendor Cloud Foundry Foundation Versions Affected Cloud Foundry v208 through v231 Login-server v1.6 - v1.14 UAA v2.0.0 - v2.7.4.1 &

CVE-2016-0780 Cloud Controller Disk Quota EnforcementSeverity *High*Vendor *Cloud Foundry Foundation*Versions Affected *cf-release v231 and lower*Description *It was discovered that Cloud Foundry

You need to register the mongo service with the marketplace. There are further instructions in that README.

Hello, Last week we completed changes to the rootfs that removed libmysqlclient in favor of replacing it with libmariadb [1]. This change was released in cf-released v233. Unfortunately,