Disable ssl verification workaround works. https://github.com/kei-yamazaki/java-buildpack/commit/6b0551ce62f3be3b60e687775554f6f5b126cd0c It can push with -b option. cf push <APP-NAME> -b

Hi all, Just an update: This affects: * users of the "online" a.k.a. "uncached" java-buildpack, * users of the "online/uncached" ruby-buildpack 1.5.0 and later who haved opted-in to JRuby. We're

Ah sorry - I wasn't able to see the image of the error on my phone. I thought it was a different error. aleksey.zalesov(a)altoros.com> wrote:

I've reported this and we're working on it. For what it's worth, this should only affect the Java build pack. I don't believe the other ones are using that URL. If you're seeing the message with

Can you clarify how can I do this? It is not problem of our installation SSL cert that can be skipped with —skip-ssl-validation. Aleksey Zalesov | CloudFoundry Engineer | Altoros Tel: (617)

Are you able to work around the issue by skipping SSL validation?

Yup - I can confirm as well. All buildpacks relying on download.run.pivotal.io are failing now. S. wrote:

Hi all, I encountered the same problem. The same problem has occurred even PWS. Please fix as soon as possible.

Hello! Today we can't push apps to CF due to expired SSL certificate of download.run.pivotal.io <http://cf-dev.70369.x6.nabble.com/file/n1404/Screen_Shot_2015-08-31_at_15.png> Here are CF app

Hi, I recently browsed through your business listing and wanted to highlight some key points for consideration. I am sure it will complement your SEOwork to help attract quality visitors and

Hi, I represent providers of high quality office coffee. By choosing a specialized coffee delivery service, you can cut your overhead noticeably vs. using grocery delivery or even wholesale

All, The existing dropsonde protocol uses a different message type for each event type. HttpStart, HttpStop, ContainerMetrics, and so on are all distinct types in the protocol definition. This

The diego ssh daemon is a statically linked binary so if you have a /bin/sh or a /bin/bash in your docker image, it should work. The scp support is also baked in so you don't need that binary at the

diego ssh support should work with docker images. there likely are some minimal prerequisites for things in the image like a shell or whatever executables you would try with ssh. here is my output

The SSH support in Diego is awesome. I'm wondering whether it's possible to SSH into a pushed Docker image as well? If yes, what need to be done in the docker image in order to get it

Excellent addition. One less reason for us to maintain our acceptance test fork. Mike wrote:

I replied a while ago but it appears the mailing list dropped it. Here is another attempt. Thanks for the response Erik. {quote} * Loggregator's dropsonde protocol didn't allow for a clean way

we've been using a new term for the same concept we've previously labeled placement pools called "isolation groups". onsi has been working on some documentation for what this may look like and the

More than a year ago, there was some discussion and a proposal around adding placement pools so cloud foundry admins could better target how applications were placed on

Hi all, In our deployment we have a number of customers who want to be able, as organization owners, to block access to specific public services from their org members. I have put together a