Quick reminder of the CAB call this Wednesday, February 10th @ 8a PDT. All info in

wrote: The administrator for the CF installation you're targeting has disabled docker support. Since you're not an administrator, you cannot turn on this feature. Talk to your administrator and

I want to deploy a Docker image in cloud Foundry. So I proceeded as below. I am using cf version 6.14.1+dc6adf6-2015-12-22. $ cf push myimage -o cloudfoundry/lattice-app --no-start Creating app

Somehow I didn't get Eric's reply so my reply above probably seems odd. Sorry Eric! wrote:

Hi, Dr Nic, This issue also came up in the #buildpacks channel in the CF Slack the other day. Until we solve this permanently, a cleaner and more complete workaround seems to be to run

Eventually I figured out a (nasty) workaround to manually load the environment: https://blog.starkandwayne.com/2016/02/07/run-one-off-tasks-and-database-migrations/ You need to run the following

+ cf-bosh Looking for community feedback on bumping consul to 0.6.0 in the consul-release maintained by the core CF team: https://github.com/cloudfoundry-incubator/consul-release. Please see

Hello, all I am running into this issue again. With change cell VM to c3.xlarge(7.5G memory), I have successfully pushed 2 applications to my cf/diego environment. app1 asked 2g memory and app2

Just as a reference you could look at some of the connection tests that Monit allows: https://mmonit.com/monit/documentation/monit.html#CONNECTION-TESTING Obviously there are quite a few there so it

Dear CF Community, CF has long had a notion of health-checking app instances as they start up to determine whether they're in a functional state, on top of the process simply having started. On the

Thanks, Aaron, that's extremely helpful. I'll start a separate thread on cf-dev shortly soliciting more input on how the community would find richer health checks useful, but this specification seems

Hello Johannes, You have observed expected behavior. Wildcard routes are designed to catch all subdomains, unless other routes (wildcard or otherwise) exist to match. Primary use cases for wildcard

Hi Dieu, I had the same plans. But the solution feels a bit like a workaround. Is this behaviour expected? If not should I try to fix it? Cheers Johannes

I have setup uaa service, and trying to setup a non-browser client (another server actually) to get the authorization. In fact, I am trying to adapt sample "login" application to my needs. However,

Hi Gwenn Thanks for your feedback, and taking the time to look through the changelog! cf-release/consul-release have been on 0.5.2 (post BoltDB migration) since Jun

Thanks Filip and Shawn. I think Filip's suggestion would solve our problem. -- http://www.twitter.com/sivabalans

My biggest concern is the Data migration from LMDB to BoltDB, I know there is a CLI to do that but I am concern about the migration of the DATA itself. *" Previously, Consul would automatically

Thank you for the additional context, Carlo. I agree the loss of support for non-TLS requests would not only restrictive, but potentially backwards incompatible. Shannon Coen Product Manager, Cloud

The only known route limitation I am aware of on a CF org is the route quota associated with the org. If you type 'cf org [ORG_NAME]' you should see how many routes are allowed. You can also view

We would potentially be affected as we use Fog's Atmos provider for now. In the future we plan to implement fully s3 compatible Object storage so no problem then but may require some backwards