OK, that makes sense. It sounds like you're installing the web app on the bare VM, and not in a container rootfs. This isn't really a supported use case for the Buildpack, which is going to make

Hi Mike, the line ```gem 'jruby-openssl', :platforms => :jruby ``` means jruby-openssl gem will be downloaded by bundler if and only if JRuby platform is detected, I am using MRI not JRuby. The

Hi Daya, I'm a bit confused, as it looks from your Gemfile like you're trying to load a JRuby openssl gem while running MRI ruby. What happens if you remove your dependency on the `jruby-openssl`

testing_openssl.rb mentioned previously is here https://gist.github.com/daya/71a589f9b83f9ff57608 CloudFoundry Ruby Build Pack 1.4 https://github.com/cloudfoundry/ruby-buildpack/releases/tag/v1.4.0

Hi There is a OpenSSL version/dependency mismatch as far as Ruby BuildPack and Stemcells are concerned Our bosh-lite environment is *StemCell*: Name:

aaron, i added a page on the cf community wiki with your links: https://github.com/cloudfoundry-community/cf-docs-contrib/wiki/Mailing-Lists wrote: -- Thank you, James Bayer

We had the similar issue with AWS. In AWS pannel we couldn't find any instance that used some IP address, still there was no ability to create an instance with such IP. We got this bug after we

Thanks.

Might want to cross-post this to cf-dev.

Was that IP previously assigned to a different VM (check via `bosh vms`)? Currently BOSH does not allow to pick a static IP if it's already in use by another VM. You could try putting it as a

Have you terminated the previous Amazon HA Proxy instance? If not, this might be the reason of the reserved IP error. -- Lev Berman Altoros - Cloud Foundry deployment, training and

Hi BOSH users! We're running into an error when attempting to re-deploy a failing BOSH deployment of CF to AWS: `ha_proxy_z1/0' asked for a static IP 52.28.90.12 but it's already reserved/in

Hi all, When deploying Cloud Foundry on OpenStack using BOSH, there is a good reference doc: http://docs.cloudfoundry.org/deploying/openstack/install_cf_openstack.html. For Diego release, is there

+! nice job! Cheers, Christopher Ferris IBM Distinguished Engineer, CTO Open Cloud IBM Software Group, Open Technologies email: chrisfer(a)us.ibm.com twitter: @christo4ferris blog:

Thanks Aaron! Chip Childers | Technology Chief of Staff | Cloud Foundry Foundation wrote:

+1 Nice work Aaron! wrote:

I've created Nabble archives of the CF lists here: http://cf-bosh.70367.x6.nabble.com/ http://cf-dev.70369.x6.nabble.com/ http://cf-lattice.70370.x6.nabble.com/ The archives are searchable and allow

Thanks Dmitriy - I guess with DEA not working there won't be any functioning CF on CentOS/RHEL. I wonder if SLES has better CF story at this point (in terms of porting)?

Cloud Foundry Elastic Runtime can only be deployed at this point on Ubuntu Trusty stemcell. All components work of ER work on CentOS stemcell except the DEA (component that runs applications) due to

I put in a request with markmail.org. Dan wrote: