vmware-archive / pcfdev Goto Github PK

This is the depricated version of PCF Dev - please visit the current Github repository https://github.com/cloudfoundry-incubator/cfdev for the latest updates

License: Apache License 2.0

Ruby 3.01% Shell 10.40% Go 85.81% Dockerfile 0.78%

pcfdev's Introduction

Update on PCF Dev

This is the deprecated version of PCF Dev - please visit the current Github repository https://github.com/cloudfoundry-incubator/cfdev for the latest updates

PCF Dev

PCF Dev is a new distribution of Cloud Foundry designed to run on a developer’s laptop or workstation. PCF Dev gives application developers the full Cloud Foundry experience in a lightweight, easy to install package. PCF Dev is intended for application developers who wish to develop and debug their application locally on a full-featured Cloud Foundry. PCF Dev is also an excellent getting started environment for developers interested in learning and exploring Cloud Foundry.

More information about the project can be found on the FAQ.

Open Source

This repository contains source code that allows developers to build an open source version of PCF Dev that only contains the Elastic Runtime and the CF MySQL Broker. The binary distribution of PCF Dev that is available on the Pivotal Network contains other PCF components (such as the Redis, RabbitMQ and Spring Cloud Services marketplace services as well as Apps Manager) that are not available in this repository.

However, we encourage you to leave any feedback or issues you may encounter regarding the full, binary distribution of PCF Dev in this repository's Github issues.

Install

Download the latest pcfdev-VERSION-PLATFORM.zip from the Pivotal Network.
Unzip the zip file and navigate to its containing folder using PowerShell or a Unix terminal.
Run the extracted binary.
Run cf dev start.

Check out the documentation for more information. Running cf dev help will display an overview of PCF Dev VM management commands.

Prerequisites

CF CLI
VirtualBox: 5.0+
Internet connection (or Dnsmasq or Acrylic) required for wildcard DNS resolution

Using the Cloud Foundry CLI Plugin

Follow the instructions provided at the end of cf dev start to connect to PCF Dev:

Downloading VM...
Progress: |====================>| 100%
VM downloaded
Importing VM...
Starting VM...
Provisioning VM...
Waiting for services to start...
40 out of 40 running
 _______  _______  _______    ______   _______  __   __
|       ||       ||       |  |      | |       ||  | |  |
|    _  ||       ||    ___|  |  _    ||    ___||  |_|  |
|   |_| ||       ||   |___   | | |   ||   |___ |       |
|    ___||      _||    ___|  | |_|   ||    ___||       |
|   |    |     |_ |   |      |       ||   |___  |     |
|___|    |_______||___|      |______| |_______|  |___|
is now running.
To begin using PCF Dev, please run:
    cf login -a https://api.local.pcfdev.io --skip-ssl-validation
Admin user => Email: admin / Password: admin
Regular user => Email: user / Password: pass

The local.pcfdev.io domain may differ slightly for your PCF Dev instance.

To stage a simple app on PCF Dev, cd into the app directory and run cf push <APP_NAME>.

See cf documentation for information on deploying apps and attaching services.

Using a customized PCF Dev OVA

Specify the path to the custom built OVA with the -o flag to the cf dev start command.

$ cf dev start -o /path/to/custom/ova
Importing VM...
Starting VM...
Provisioning VM..
...

To build a custom PCF Dev OVA, please see our DEVELOP Documentation.

Uninstall

To temporarily stop PCF Dev run cf dev stop.

To destroy your PCF Dev VM run cf dev destroy.

To uninstall the PCF Dev cf CLI plugin run cf uninstall-plugin pcfdev

Contributing

If you are interested in contributing to PCF Dev, please refer to the contributing guidelines and development instructions.

Copyright

PCF Dev uses a version of Monit that can be found here, under the GPLv3 license.

pcfdev's People

Contributors

Stargazers

Watchers

Forkers

mpivotal tushar-dadlani agilemobiledev sergiubodiu nunb hostirosti felipeg48 nagyistoce reagul mnenad tbh1 mgunter-pivotal souravbh morika-t timani springyboing sneal raulavila lummie tichimura-pivotal npatel27 o-orand thomasdarimont lehoanganh nota-ja mattjcurry supraron sleighsoft lwoydziak ubergeekcd comdaze datianshi chetankumarmore kulpree handong890 ebabani lmacc ivandavidov cf-container-networking nitinreddy3 svrc kumardevsai calebwashburn jkujovic reshnm a12o ftroncosom malejandromorenov shashankreddysunkara muliravi petereltgroth strikingraghu rkparuchuri gehendrasharma dystudio explore-dot-net lakeplacidkcsb aemengo dander521 isabella232 iq-scm

pcfdev's Issues

Enable Google vagrant provider for deploy to Google Cloud Platform

Hi,

I'm working on enabling micropcf to be deployed to Google Cloud Platfrom. The Vagrantfile part is almost done. Who can help / whom can I contact for creating a micropcf/base GCP image?

security-group for specific access

Hello,

I tried to access external DB(192.168.67.2:3306) from container,
but security-group is not working that i expected.
this is how to reproduce:

env: micropcf base 0.28.0

sshed into micropcf(192.168.11.11) and set iptables:
iptables -A INPUT -p tcp -m tcp --dport 3306 -j ACCEPT
iptables -t nat -A PREROUTING -d 192.168.11.11 -p tcp --dport 3306 -j DNAT --to-destination 192.168.67.2:3306
iptables -t nat -A POSTROUTING -j MASQUERADE
I set security group as following, but not working
[{"protocol":"tcp","destination":"192.168.11.0/24","ports":"3306"}]
cf create-security-group mysql mysql-sg
cf bind-security-group mysql micropcf-org micropcf-space
cf bind-staging-security-group mysql
cf bind-running-security-group mysql

alternatively if I set all_open security group then it works, ( which is the same with PCF default security group)
[{"destination": "0.0.0.0-255.255.255.255","protocol": "all"}]

thanks.

Proper method to shutdown virtualbox

This is a request to include a little more documentation that explains among other things the proper method for shutting down the vm in virtualbox. I am unable to ascertain the credentials for logging into the virtual machine to issue a shutdown command.

Vagrant up terminates abruptly

I tried the builds from Jan-29 and also some from Dec-18th, however i haven't been successful in bringing up Micropcf. I am running this on MacBook Pro and using Virtualbox.

Here's the error I get:

user@macbook-pro:~/code/micropcf|
⇒ VM_CORES=4 VM_MEMORY=2500MB vagrant up --provider=virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Configuring and enabling network interfaces...
==> default: Machine already provisioned. Run vagrant provision or use the --provision
==> default: flag to force provisioning. Provisioners marked to run always will still run.

The Vagrant VM is running (i am able to login to it via VirtualBox), but i am not able to do a cf login.

⇒ cf api api.local.micropcf.io --skip-ssl-validation
Setting api endpoint to api.local.micropcf.io...
FAILED
Error performing request: Get http://api.local.micropcf.io/v2/info: dial tcp: lookup api.local.micropcf.io: no such host

Name on the CLI should be 'micropcf', not 'default'

This is a bit confusing:

$ vagrant destroy
default: Are you sure you want to destroy the 'default' VM? [y/N] y

Linux - Number of CPUs used is inefficient

uniq removes sequentially duplicated lines, therefore input needs sorting first to achieve a unique count.
Optimum vcpu number in vm should not include hyperthread cpu therefore calculation should be physical cpus * cores on each cpu
e.g. I have 2 x 8 core CPUs (hyperthreaded too) currently returns 32, should be 16.

Question: Does micropcf include the PCF apps manager?

First of all, thanks for providing microPcf. It is very easy to install and seems like a great starting point.

Yet I have a couple of questions:

Does it include the Apps manager, that is provided in ordinary PCF installations? If yes, how do I access it?
What is the difference to bosh-lite? This is the local cloudfoundry installation I was working previously with.
What is the cloudfoundry version it provides? Is the current version already running diego?

Would it make sense to answer those questions in a FAQ in the Wiki. If yes, I would be glad to put it there.

Thanks!

Question: can I use uaac with micropcf for registering new clients?

I am trying to do: uaac token client get admin

such that I can subsequently register a new client with the uaa. What is the password?

Or is there a different way to register new uaa clients?

The application should be able manage additional information for the CF user.

"no available version" error when doing `vagrant up`

At least with the virtualbox provider,

 ❯ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'micropcf/base' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: 0
==> default: Loading metadata for box 'micropcf/base'
    default: URL: https://atlas.hashicorp.com/micropcf/base
The box you're attempting to add has no available version that
matches the constraints you requested. Please double-check your
settings. Also verify that if you specified version constraints,
that the provider you wish to use is available for these constriants.

Box: micropcf/base
Address: https://atlas.hashicorp.com/micropcf/base
Constraints: 0
Available versions: 0.0.1, 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.5.0, 0.6.0, 0.7.0, 0.8.0, 0.9.0, 0.10.0, 0.11.0, 0.12.0, 0.13.0, 0.14.0, 0.16.0, 0.17.0, 0.18.0, 0.19.0, 0.20.0, 0.21.0, 0.22.0, 0.23.0, 0.24.0, 0.26.0, 0.27.0, 0.28.0, 0.29.0, 0.30.0, 0.31.0, 0.32.0, 0.33.0, 0.34.0, 0.35.0, 0.36.0, 0.37.0, 0.38.0, 0.39.0, 0.40.0, 0.41.0, 0.42.0, 0.44.0, 0.45.0, 0.46.0, 0.47.0, 0.48.0, 0.49.0, 0.50.0, 0.51.0, 0.52.0, 0.53.0, 0.54.0, 0.55.0, 0.56.0, 0.57.0

config.vm.box_version = "0" inside Vagrantfile may be at issue. Editing this and hard-coding one of the versions (e.g. config.vm.box_version = "0.57.0") gets past this.

If I find a generic way to handle it, I'll fork and submit a pull request.

"502 Bad Gateway: Registered endpoint failed to handle the request."

This morning, I downloaded 0.2.0 from the releases page and ran

vagrant up --provider virtualbox

Everything seemed to come up OK:

µPCF $ vagrant up --provider virtualbox-provider virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'micropcf/base' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: 0.4.0
==> default: Loading metadata for box 'micropcf/base'
    default: URL: https://atlas.hashicorp.com/micropcf/base
==> default: Adding box 'micropcf/base' (v0.4.0) for provider: virtualbox
    default: Downloading: https://atlas.hashicorp.com/micropcf/boxes/base/versions/0.4.0/providers/virtualbox.box
==> default: Successfully added box 'micropcf/base' (v0.4.0) for 'virtualbox'!
==> default: Importing base box 'micropcf/base'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'micropcf/base' is up to date...
==> default: Setting the name of the VM: PCF_default_1449844513694_72448
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
    default: 
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default: 
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Configuring and enabling network interfaces...
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
==> default: Waiting for services to start...
==> default: MicroPCF is now running.
==> default: To begin using MicroPCF, please run:
==> default:    cf api api.local.micropcf.io --skip-ssl-validation
==> default:    cf login
==> default: Email: admin
==> default: Password: admin

But:

µPCF $ cf api api.local.micropcf.io --skip-ssl-validation
Setting api endpoint to api.local.micropcf.io...
FAILED
Server error, status code: 502, error code: 0, message:

Any ideas what's going on?

Support Windows cells to allow .NET app deployments

It would be great if we had a systematic way to enable micropcf to allow Windows Cells to be added to it to allow hosting for .NET applications.

I am able to do this today (manually, and somewhat unreliably) if I create a separate Windows 2012R2 VM, use the GardenWindows.msi and DiegoWindows.msi from network.pivotal.com, and point them to the 172.x.x.x address that micropcf is running on for Consul and etcd. Additionally, I need to modify the config of cloud_controller_ng to add a section to the stacks.yml to enable the windows2012R2 stack:

default: cflinuxfs2
stacks: 
- description: Cloud Foundry Linux-based filesystem
  name: cflinuxfs2
- description: Windows Server 2012 R2
  name: windows2012R2

It would be really cool if there was an option to either enable this stack when the box is being configured, or perhaps even make it the default in the config file for ccng.

Naming question?

The name of the project is MicroPCF, implying, at least to me, that this is based on and an example of PCF, or Pivotal's version of Cloud Foundry.

However, looking through the build and other sources, it appears to be standard opensource-based CF.

So, is it based on PCF and I've missed it? Or is the name implying something incorrect?

--M

MongoDB / Cassandra / BOSH support

Any plans for including NoSQL databases such as MongoDB and Cassandra in the near future releases of pcfdev?
I'm considering using cups command to provide MongoDB access.
But would like to get a default MongoDB database available as a service in marketplace with pcfdev.

Also, when are we going to see the access to bosh shell or bosh director?
I want to create my own bosh scripts for setting up 'Spring Cloud Services' in pcfdev.

Unable to connect to the external network

I have created a user provided service for my redis server running in my host machine.

redis://:[email protected]:6379
192.168.1.6 - Host machine ip address

I'm able to connect to my redis server from my guest machine.

vagrant ssh
Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.19.0-43-generic x86_64)
 * Documentation:  https://help.ubuntu.com/
Last login: Fri Jan 29 16:36:51 2016 from 10.0.2.2
vagrant@agent-id-micropcf-0:~$ redis-cli -h 192.168.1.6 -p 6379
192.168.1.6:6379>

But my spring boot app deployed in my micropcf is unable to connect to above redis server.

herServlet]    : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is org.springframework.data.redis.RedisConnectionFailureException: Cannot get Jedis connection; nested exception is redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool] with root cause
2016-01-29T22:23:15.68+0530 [APP/0]      OUT java.net.ConnectException: Connection refused

I think there is some network issue with application running within the container to access the external network or is there any other way I should be connecting to the external world for the services?

Doubts

Is pcf console available?
Is there a way to install services in the market place?
If we want to bind to rabbitmq, redis services, how to do that in this case? Is set-env for an application work?

Note: Please label this entry as questions. I don't see an option to do it myself.

Future of micropcf: Docker, Otto, Docker Vagrant provider?

Discussion thread
MicroPCF seems to be a great project for getting a development environment up and running moderately quickly.

Currently I am using bosh-lite, where I had to buy an extra 8GB of RAM, and then it only took ~90 minutes to install everything (cf v230 and diego). The VM allocated 6144MB of memory for itself, and 4 CPUs. I note that your Vagrantfile uses 25% of host memory, and all CPUs.

In production deployments there's a multitude of specialised nodes.

Why don't we make our dev install micro-service orientated?

Options
Here are the primary options I can think of, add yours if its not below:

An 'ocean' of Dockerfiles, orchestrated trivially (we're talking one host afterall)
Otto (Hashicorp's Vagrant successor; uses Vagrant beneath-the-scenes)
Vagrant providers (includes Docker)

Disadvantages

Different to current approach
Development required

Advantages

Easier to isolate and test individually, and progressively test with more dependent components
Less system overhead
Smaller file-size (great for sharing 'snapshots' across development teams)

DEVELOP.md

Can you please add

Go (and the min version)
jq (and the min version)
to the dependencies for building.

Also aws is required (even if you are not building for AWS e.g. build -only=virtualbox-iso)

Reboot removes all data?

I'm not sure if this is the expected behaviour... but when I reboot my microPCF instance it loses all the data and starts from scratch. I had defined a custom space, created and pushed an offline buildpack and then pushed two applications. When I reboot the VM it comes back completely pristine as if I had just started it.

$ cf spaces
Getting spaces in org cf.maltson.com-org as admin...

name
No spaces found

Is this expected? Is there any way to turn this off and have microPCF preserve the data between reboots? Thank you.

Support for VMware Fusion

Would be nice to use getopt in the start-osx script to set a flag --provider=vmware_fusion

Trying to vagrant up on AWS

I'm getting the error below when I try to vagrant up on AWS. I can vagrant SSH into the VM and I have 386 processes running. When I try to cf api --skip-ssl-validation http://Ext.IP.xip.io I get a 404 not found error. Ideas or log files to review?

Bringing machine 'default' up with 'aws' provider...
==> default: Checking if box 'micropcf/base' is up to date...
==> default: Warning! The AWS provider doesn't support any of the Vagrant
==> default: high-level network configurations (config.vm.network). They
==> default: will be silently ignored.
==> default: Launching an instance with the following settings...
==> default: -- Type: m4.large
==> default: -- AMI: ami-1712467d
==> default: -- Region: us-east-1
==> default: -- Keypair: vagrant
==> default: -- Block Device Mapping: []
==> default: -- Terminate On Shutdown: false
==> default: -- Monitoring: false
==> default: -- EBS optimized: true
==> default: -- Source Destination check:
==> default: -- Assigning a public IP address in a VPC: false
==> default: -- VPC tenancy specification: default
==> default: Waiting for instance to become "ready"...
==> default: Waiting for SSH to become available...
==> default: Machine is booted and ready for use!
==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default:
==> default:
==> default: %
==> default:
==> default: T
==> default: o
==> default: t
==> default: a
==> default: l
==> default:
==> default:
==> default:
==> default:
==> default: %
==> default:
==> default: R
==> default: e
==> default: c
==> default: e
==> default: i
==> default: v
==> default: e
==> default: d
==> default:
==> default: %
==> default:
==> default: X
==> default: f
==> default: e
==> default: r
==> default: d
==> default:
==> default:
==> default: A
==> default: v
==> default: e
==> default: r
==> default: a
==> default: g
==> default: e
==> default:
==> default: S
==> default: p
==> default: e
==> default: e
==> default: d
==> default:
==> default:
==> default:
==> default: T
==> default: i
==> default: m
==> default: e
==> default:
==> default:
==> default:
==> default:
==> default: T
==> default: i
==> default: m
==> default: e
==> default:
==> default:
==> default:
==> default:
==> default:
==> default: T
==> default: i
==> default: m
==> default: e
==> default:
==> default:
==> default: C
==> default: u
==> default: r
==> default: r
==> default: e
==> default: n
==> default: t
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default: D
==> default: l
==> default: o
==> default: a
==> default: d
==> default:
==> default:
==> default: U
==> default: p
==> default: l
==> default: o
==> default: a
==> default: d
==> default:
==> default:
==> default:
==> default: T
==> default: o
==> default: t
==> default: a
==> default: l
==> default:
==> default:
==> default:
==> default: S
==> default: p
==> default: e
==> default: n
==> default: t
==> default:
==> default:
==> default:
==> default:
==> default: L
==> default: e
==> default: f
==> default: t
==> default:
==> default:
==> default: S
==> default: p
==> default: e
==> default: e
==> default: d
==> default:
==> default:
==> default: 0
==> default:
==> default:
==> default:
==> default:
==> default:
==> default: 0
==> default:
==> default:
==> default:
==> default:
==> default: 0
==> default:
==> default:
==> default:
==> default:
==> default:
==> default: 0
==> default:
==> default:
==> default:
==> default:
==> default: 0
==> default:
==> default:
==> default:
==> default:
==> default:
==> default: 0
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default: 0
==> default:
==> default:
==> default:
==> default:
==> default:
==> default:
==> default: 0
==> default:
==> default: -
==> default: -
==> default: :
==> default: -
==> default: -
==> default: :
==> default: -
==> default: -
==> default:
==> default: -
==> default: -
==> default: :
==> default: -
==> default: -
==> default: :
==> default: -
==> default: -
==> default:
==> default: -
==> default: -
==> default: :
==> default: -
==> default: -
==> default: :
==> default: -
==> default: -
==> default:
==> default:
==> default:
==> default:
==> default:
==> default: 0
100 13 100 13 0
==> default: 0 3869 0 --
==> default: :--:-- --:--:-
==> default: - --:--:--
==> default: 4333
==> default: Waiting for services to start...
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Redis Service

Is there a limit to the number of connections that can be made to the Redis service in PCFDev? If so is this configurable?

Micro pcf's cert blocks cloudfoundry Java client library

The cert served breaks cloudfoundry-java-lib:

org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://api.local.micropcf.io/info":Certificate for <api.local.micropcf.io> doesn't contain CN or DNS subjectAlt; nested exception is javax.net.ssl.SSLException: Certificate for <api.local.micropcf.io> doesn't contain CN or DNS subjectAlt
    at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:580)
    at org.cloudfoundry.client.lib.rest.LoggingRestTemplate.doExecute(LoggingRestTemplate.java:54)
    at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:530)
    at org.springframework.web.client.RestTemplate.getForObject(RestTemplate.java:237)

This call has the self signed cert check disabled so this is something else. I'm hoping that mending the cert is all it takes to connect through our standard library.

Proper command to start pcfdev with AWS provider

What is the recommended way to initialize and start pcfdev using AWS as the provider.

I can obviously modify start-osx.sh to use the --provider=aws argument on the vagrant up command, but wonder if that is the preferred approach.

I attempted to use ./start-osx --provider=aws but that resulted in using the virtualbox provider.

I have been successful in starting pcfdev using AWS as provider so far only by modifying the .start-osx script and populating the environment variables needed by the AWS section of the Vagrantfile.

--M

Cloud lattice vs pcfdev - which one to use and for what usecase?

Hi,

In what way is pcfdev different from cloud lattice.

Seems like both have same objectives.

I am not clear which one would be better to install and explore cloud foundary features locally with a laptop.

I was planning to install cloud lattice after googling about a way to explore cloud foundary locally.

Can you help in clarifying the scope of 2 products and the usecases in which pcfdev would be better.

Thanks,
Volivattam

Not able to access the https://api.local.pcfdev.io/ in browser. Shows the below responce.

{
"code": 10000,
"description": "Unknown request",
"error_code": "CF-NotFound"
}

Cannot start - issue on download

Trying v0.14.0 - I have the below error (I tried from 2 networks) - after around 1 hour of download

==> default: Adding box 'pcfdev/pcfdev' (v0.54.0) for provider: vmware_desktop
default: Downloading: https://atlas.hashicorp.com/pcfdev/boxes/pcfdev/versions/0.54.0/providers/vmware_desktop.box
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
SSL read: error:00000000:lib(0):func(0):reason(0), errno 54

Issue trying NGinx docker image

I am trying to test docker support in Diego and I am facing issues because the ports used by the docker images. In my case, trying with NGinx:

cf push NGinx -o nginx

But it fails...

2016-02-01T10:31:26.61+0100 [CELL/0] OUT Successfully created container
2016-02-01T10:31:26.61+0100 [CELL/0] OUT Starting health monitoring of container
2016-02-01T10:31:27.17+0100 [HEALTH/0] OUT healthcheck failed
2016-02-01T10:31:27.18+0100 [HEALTH/0] OUT healthcheck passed
2016-02-01T10:31:27.18+0100 [HEALTH/0] OUT Exit status 1
2016-02-01T10:31:27.19+0100 [HEALTH/0] OUT Exit status 0
2016-02-01T10:31:27.72+0100 [HEALTH/0] OUT healthcheck failed
...............
...............
2016-02-01T11:29:41.46+0100 [API/0] OUT App instance exited with guid 35def1d1-1190-404d-ad85-075cff5945c1 payload: {"instance"=>"eeb17051-85a1-47ef-721d-1b61e068aa86", "index"=>0, "reason"=>"CRASHED", "exit_description"=>"2 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* Exited with status 1\n* 2 error(s) occurred:\n\n* cancelled\n* cancelled", "crash_count"=>3, "crash_timestamp"=>1454322581441417609, "version"=>"a9771553-ced6-40a4-8e2c-c9ff25af5282"}

When trying again I get:

Updating app NGinx in org micropcf-org / space micropcf-space as admin...
FAILED
Server error, status code: 400, error code: 100001, message: The app is invalid: ports Ports must be in the 1024-65535.

I understand the issue is that NGinx by default tries to use port 80.

Thanks in advance!

MicroPCF doesn't start without Internet connectivity

As requested by @davidwadden in #17 here it is a new issue:
Environment:
MicroPCF 0.5.0
Vagrant 1.8.1
VBox 5.0.14
Windows 7

When I start MicroPCF with Internet connectivity, after 5-6 minutes MicroPCF starts successfully.

If I try to start it without Internet connectivity, it gets stuck at:
==> default: Waiting for services to start...

After 12-14 minutes it still at that point. And as soon as I plug the ethernet (Internet connectivity) it finishes successfully. If I don't attach the ethernet which not always is possible it never finishes.

Don't know if this is an issue or not. I understand I need Internet connectivity to get a new buildpack or a docker image from the community, but if I just want to test my own things locally with no external interaction, should it work?

Not able to login in PCF Dev. Server error, status code: 403, error code: 0,

PCF Dev has reserved 3 GB out of 7 GB total system memory.
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'pcfdev/pcfdev' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Configuring and enabling network interfaces...
==> default: Machine already provisioned. Run vagrant provision or use the --provision
==> default: flag to force provisioning. Provisioners marked to run always will still run.
==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: Waiting for services to start...
==> default: 0 out of 48 running
==> default: 0 out of 48 running
==> default: 0 out of 48 running
==> default: 0 out of 48 running
==> default: 0 out of 48 running
==> default: 38 out of 48 running
==> default: 48 out of 48 running
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
PS C:\00PCE5COB\PCF\pcfdev-v0.15.0> cf api api.local.pcfdev.io --skip-ssl-validation
Setting api endpoint to api.local.pcfdev.io...
FAILED
Server error, status code: 403, error code: 0, message:

http proxy settings not used in container

I'm trying to spin up a micropcf, but we're behind an HTTP proxy. I noticed with the released Vagrant file that it's using the same setup as Lattice with regards to the vagrant-proxyconf plugin. I vagrant up the machine with http_proxy and https_proxy exported, and find that micropcf starts correctly and when I vagrant ssh the proxy settings are set.

vagrant@micropcf:~$ echo $http_proxy
http://proxy:3128
vagrant@micropcf:~$ echo $https_proxy
http://proxy:3128
vagrant@micropcf:~$ echo $no_proxy
localhost,127.0.0.1,192.168.11.11,local.micropcf.io

I've also left the http(s) proxy and no_proxy settings on my Mac too before pushing.

arthur@hephaestus $ echo $http_proxy
http://proxy:3128
arthur@hephaestus $ echo $https_proxy
http://proxy:3128
arthur@hephaestus $ echo $no_proxy
localhost,127.0.0.1,192.168.11.11,local.micropcf.io

But when I push up the application, which is just a simple Ruby app, it fails to download bundler. But I can download bundler from the VM itself:

vagrant@micropcf:~$ wget https://pivotal-buildpacks.s3.amazonaws.com/ruby/binaries/shared/bundler-1.9.7.tgz
--2015-12-14 21:21:19--  https://pivotal-buildpacks.s3.amazonaws.com/ruby/binaries/shared/bundler-1.9.7.tgz
Resolving monty.ms.otpp.net (monty.ms.otpp.net)... 10.254.204.104, 10.254.204.104
Connecting to monty.ms.otpp.net (monty.ms.otpp.net)|10.254.204.104|:3128... connected.
Proxy request sent, awaiting response... 200 OK
Length: 244764 (239K) [binary/octet-stream]
Saving to: ‘bundler-1.9.7.tgz’

100%[====================================================================================================================================================================================================================================>] 244,764     --.-K/s   in 0.1s

2015-12-14 21:21:20 (1.83 MB/s) - ‘bundler-1.9.7.tgz’ saved [244764/244764]

It just seems that the proxy settings aren't making their way to the garden containers. I poked around a bit to see where garden is being initialized, but I haven't found anything yet (no upstart/init script I can see).

Here's the full logs from the push:

arthur@hephaestus $ cf push badges
Creating app badges in org local.micropcf.io-org / space test as admin...
OK

Using route badges.local.micropcf.io
Binding badges.local.micropcf.io to badges...
OK

Uploading badges...
Uploading app files from: /Users/arthur/work/ruby/badges
Uploading 10.9K, 21 files
Done uploading
OK

Starting app badges in org local.micropcf.io-org / space test as admin...
Creating container
Successfully created container
Downloading app package...
Downloaded app package (7.2K)
No buildpack specified; fetching standard buildpacks to detect and build your application.
Downloading buildpacks (ruby_buildpack, nodejs_buildpack, go_buildpack, python_buildpack, php_buildpack, staticfile_buildpack, binary_buildpack, java_buildpack)...
Downloading python_buildpack...
Downloading nodejs_buildpack...
Downloading php_buildpack...
Downloading ruby_buildpack...
Downloaded ruby_buildpack
Downloading go_buildpack...
Downloaded php_buildpack
Downloading staticfile_buildpack...
Downloaded python_buildpack
Downloading binary_buildpack...
Downloaded staticfile_buildpack
Downloading java_buildpack...
Downloaded binary_buildpack
Downloaded java_buildpack
Downloaded nodejs_buildpack
Downloaded go_buildpack
Downloaded buildpacks
Staging...
cat: ../VERSION: No such file or directory
-------> Buildpack version 1.6.9
       Downloaded [https://pivotal-buildpacks.s3.amazonaws.com/ruby/binaries/shared/bundler-1.9.7.tgz]
 !
/tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/shell_helpers.rb:50:in `run!': Command: 'set -o pipefail; curl --fail --retry 3 --retry-delay 1 --connect-timeout 10 --max-time 90 https://pivotal-buildpacks.s3.amazonaws.com/ruby/binaries/shared/bundler-1.9.7.tgz -s -o - | tar zxf - ' failed unexpectedly: (LanguagePack::Fetcher::FetchError)
 !     Command: 'set -o pipefail; curl --fail --retry 3 --retry-delay 1 --connect-timeout 10 --max-time 90 https://pivotal-buildpacks.s3.amazonaws.com/ruby/binaries/shared/bundler-1.9.7.tgz -s -o - | tar zxf - ' failed unexpectedly:
 !
 !     gzip: stdin: unexpected end of file
 !     tar: Child returned status 1
 !     tar: Error is not recoverable: exiting now
 !
gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/fetcher.rb:24:in `fetch_untar'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/helpers/bundler_wrapper.rb:118:in `block (2 levels) in fetch_bundler'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/helpers/bundler_wrapper.rb:117:in `chdir'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/helpers/bundler_wrapper.rb:117:in `block in fetch_bundler'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:18:in `block (2 levels) in instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:40:in `yield_with_block_depth'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:17:in `block in instrument'
        from /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:16:in `instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/helpers/bundler_wrapper.rb:84:in `instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/helpers/bundler_wrapper.rb:114:in `fetch_bundler'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/helpers/bundler_wrapper.rb:33:in `install'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/ruby.rb:32:in `bundler'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/rails5.rb:9:in `block in use?'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:18:in `block (2 levels) in instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:40:in `yield_with_block_depth'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:17:in `block in instrument'
        from /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:16:in `instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/base.rb:48:in `instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/rails5.rb:8:in `use?'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack.rb:17:in `block (2 levels) in detect'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack.rb:16:in `each'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack.rb:16:in `detect'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack.rb:16:in `block in detect'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:18:in `block (2 levels) in instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:40:in `yield_with_block_depth'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:17:in `block in instrument'
        from /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:16:in `instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack.rb:13:in `detect'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/bin/compile:19:in `block in <main>'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:35:in `call'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:35:in `block in trace'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:18:in `block (2 levels) in instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:40:in `yield_with_block_depth'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:17:in `block in instrument'
        from /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:16:in `instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:35:in `trace'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/bin/compile:18:in `<main>'
Failed to compile droplet
Exit status 223
Staging failed: Exited with status 223

FAILED
BuildpackCompileFailed

Vagrantfile constaint box version "0"

I would suggest changing this constraint to the correct version with config.vm.box_version=X or just remove the constraint.

$ vagrant up                                                                             
Bringing machine 'default' up with 'virtualbox' provider...                              
==> default: Box 'micropcf/base' could not be found. Attempting to find and install...   
    default: Box Provider: virtualbox                                                    
    default: Box Version: 0                                                              
==> default: Loading metadata for box 'micropcf/base'                                    
    default: URL: https://atlas.hashicorp.com/micropcf/base                              
The box you're attempting to add has no available version that                           
matches the constraints you requested. Please double-check your                          
settings. Also verify that if you specified version constraints,                         
that the provider you wish to use is available for these constriants.                    

Box: micropcf/base                                                                       
Address: https://atlas.hashicorp.com/micropcf/base                                       
Constraints: 0                                                                           
Available versions: 0.0.1, 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.5.0, 0.6.0

Fail to access other apps that deployed in micropcf

I've two apps deployed in micropcf, one trying to access the other, but fails with ‘No route to host’

Permissions on mysql service - INSERT command denied

After creating a mysql service in my local pcfdev instance:

cf create-service p-mysql mysql-dev

and binding it to my app:

cf bind-service app mysql-dev

and pushing my app to the local pcf instance

cf push

I can create my database with the DDL statements inside schema-mysql.sql file.

However, my DML statements in my data-mysql.sql file are not being executed because of this error:

INSERT command denied to user '2S0DxFu1C8NdVrXf'@'10.254.0.6' for table 'MYTABLE'

I cannot seem to give this user enough grants in order to insert the data...

I'm using Spring Boot and Spring Data to load the data at startup

MicroPCF becoming unavailable after laptop sleep (Mac OS X)

With MicroPCF v0.6.0, I'm intermittently seeing the instance fail when my laptop returns from sleep. Vagrant reports the VM to be healthy, but the API and apps are unavailable.

VirtualBox Version 5.0.14 r105127
Vagrant 1.8.1
MicroPCF v0.6.0
OSX 10.11.3

Error starting cf-mysql-broker

We're running the latest nightly build - micropcf-v0.6.0-18-g0b99532 and seeing the following error starting the broker:

mysql_broker already exists


rake aborted!
JSON::ParserError: 776: unexpected token at '<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/json_pure-1.8.2/lib/json/common.rb:155:in `parse'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/json_pure-1.8.2/lib/json/common.rb:155:in `parse'
/var/vcap/data/packages/cf-mysql-broker/cd3a16e99fe291ce91fffe8af81f26d457829bd5-43b20ed10dce4af2eefb8431c390addb046b27e4/app/models/cloud_controller_http_client.rb:16:in `get'
/var/vcap/data/packages/cf-mysql-broker/cd3a16e99fe291ce91fffe8af81f26d457829bd5-43b20ed10dce4af2eefb8431c390addb046b27e4/lib/configuration.rb:28:in `cc_api_info'
/var/vcap/data/packages/cf-mysql-broker/cd3a16e99fe291ce91fffe8af81f26d457829bd5-43b20ed10dce4af2eefb8431c390addb046b27e4/lib/configuration.rb:17:in `auth_server_url'
/var/vcap/data/packages/cf-mysql-broker/cd3a16e99fe291ce91fffe8af81f26d457829bd5-43b20ed10dce4af2eefb8431c390addb046b27e4/config/initializers/omniauth.rb:10:in `block in <top (required)>'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/rack-1.5.5/lib/rack/builder.rb:55:in `instance_eval'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/rack-1.5.5/lib/rack/builder.rb:55:in `initialize'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/omniauth-1.2.2/lib/omniauth/builder.rb:6:in `initialize'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/actionpack-4.0.13/lib/action_dispatch/middleware/stack.rb:43:in `new'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/actionpack-4.0.13/lib/action_dispatch/middleware/stack.rb:43:in `build'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/actionpack-4.0.13/lib/action_dispatch/middleware/stack.rb:118:in `block in build'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/actionpack-4.0.13/lib/action_dispatch/middleware/stack.rb:118:in `each'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/actionpack-4.0.13/lib/action_dispatch/middleware/stack.rb:118:in `inject'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/actionpack-4.0.13/lib/action_dispatch/middleware/stack.rb:118:in `build'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/railties-4.0.13/lib/rails/engine.rb:495:in `app'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/railties-4.0.13/lib/rails/application/finisher.rb:34:in `block in <module:Finisher>'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/railties-4.0.13/lib/rails/initializable.rb:30:in `instance_exec'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/railties-4.0.13/lib/rails/initializable.rb:30:in `run'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/railties-4.0.13/lib/rails/initializable.rb:55:in `block in run_initializers'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/railties-4.0.13/lib/rails/initializable.rb:54:in `run_initializers'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/railties-4.0.13/lib/rails/application.rb:215:in `initialize!'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/railties-4.0.13/lib/rails/railtie/configurable.rb:30:in `method_missing'
/var/vcap/data/packages/cf-mysql-broker/cd3a16e99fe291ce91fffe8af81f26d457829bd5-43b20ed10dce4af2eefb8431c390addb046b27e4/config/environment.rb:5:in `<top (required)>'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:229:in `require'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:229:in `block in require'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:214:in `load_dependency'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:229:in `require'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/railties-4.0.13/lib/rails/application.rb:189:in `require_environment!'
/var/vcap/packages/cf-mysql-broker/vendor/bundle/ruby/2.2.0/gems/railties-4.0.13/lib/rails/application.rb:260:in `block in run_tasks_blocks'
Tasks: TOP => db:migrate => environment
(See full trace by running task with --trace)
Migrations failed at Mon Feb 22 21:27:58 UTC 2016```

How to update the default DNS server config?

I'd like to put my micropcf on my laptop, and I may need to demo to my customer in some place with no external network access, so the default 8.8.8.8 may not work.

Not able to target uaac url

Hi,

I have deployed cloudfoundry following this approach and it is working for me.

cf api https://api.local.micropcf.io --skip-ssl-validation

Setting api endpoint to https://api.local.micropcf.io...
OK

API endpoint: https://api.local.micropcf.io (API version: 2.44.0)
User: admin
Org: micropcf-org
Space: micropcf-space

But when I try to use the uaa url and try to target the uaa url, it fails.

uaac target https://uaa.local.micropcf.io --skip-ssl-validation

failed to access https://uaa.local.micropcf.io: Net::ReadTimeout

I am sitting behind a proxy but that doesn't restrict me when accessing cf api. Is it a problem with cf-uaac proxy settings ? What am I missing here?

Error while running Vagrant up

Hi,
I followed the github tutorial to deploy micropcf on my local system.

when i run Vagrant up from the micropcf dir, it shows the following error.

Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

shell provisioner:

The following settings shouldn't exist: run

Could anyone tell me what is the reason for this error and how to fix it ?

Adding own bosh-releases to MicroPCF, and e.g.: diego-release?

How do I add my own bosh-releases to MicroPCF?

Would be handy for sharing internal development environments around, and updating CF to the latest development (or stable, e.g.: v231) version.

Thanks for all suggestions

PS: Yes I have seen https://github.com/pivotal-cf/micropcf/blob/master/DEVELOP.md

MICRO_PCF_ON_WINDOWS

Hello All,
Its great to have the Running Cloud version on our Laptop. Great work. Will these Micro PCF can we try installing on Windows? Am seeing everybody is trying it on Linux or Mac only. Can anyone clarify on this, also share the working steps for Windows too. Thanks.

Not able to install pcf dev on my laptop

Hi,

I just got access to download pcf dev from pivotal network.

I have a few questions on getting started.

What would be the minimum RAM requirements and storage space required for it.

When i tried to install it is just taking a lot of time , it says around 5 to 6 hrs for downloading the dependencies and it got stopped many times in between.

So wanted to know if i have the required infrastructure as required for using it.

Thanks,
Sridhar

compatible buildpack error

Hi,
i'm using PCF-dev. tried to push a java app to my space and got the following error:
Staging...
None of the buildpacks detected a compatible application
Exit status 222
Staging failed: Exited with status 222
FAILED
NoAppDetectedError

i've updated the java-offline buildpack to version 3.7.1 but it didn't help:

PS C:\Users\shmary\Downloads\apps> cf buildpacks
Getting buildpacks...
buildpack position enabled locked filename
java_buildpack 1 true false java-buildpack-offline-v3.7.1.zip
ruby_buildpack 2 true false ruby_buildpack-cached-v1.6.16.zip
nodejs_buildpack 3 true false nodejs_buildpack-cached-v1.5.11.zip
go_buildpack 4 true false go_buildpack-cached-v1.7.5.zip
python_buildpack 5 true false python_buildpack-cached-v1.5.5.zip
php_buildpack 6 true false php_buildpack-cached-v4.3.10.zip
staticfile_buildpack 7 true false staticfile_buildpack-cached-v1.3.6.zip
binary_buildpack 8 true false binary_buildpack-cached-v1.0.1.zip
PS C:\Users\shmary\Downloads\apps>

any help will be appreciated !
thanks,
yaron

Meta: PivotalTracker issues aren't public viewable

Create a new account and see if you can view this issue:

Upon restart of the host, vagrant fails to bring micropcf back up

Upon restart of the host, vagrant fails to bring micropcf back up and a full reprovision (vagrant destroy / vagrant up) is necessary.
Upon restart of the host, cf target will fail, with the CC rest services down. "vagrant up" claims the machine is already up and running, and "vagrant reload" won't help either.

pcfdev fails to start all services with AWS provider

Started pcfdev using start-osx script after modifying the start command to specify --provider=aws and confirming required environment variables were populated.

VM is created successfully and provisioning script is started.

46 of 48 services are started successfully, but after hours, the remaining two have not started.
Command cf api <public DNS name> --skip-ssl-validation fails with a 404 error

Gist: https://gist.github.com/mdcarlson/ff9fb0cadc665271c6cb703a2491dfab#file-pcfdev-console-log-txt

Monit summary on the AWS pcfdev instance shows that cf-mysql-broker and quota-enforcer were in a not monitored state. MySQL appears to be failing to start due to an error attempting to connect to the mysql-_broker at mysql.local.pcfdev.io in the mysql-broker-dbcreate and mysql-broker-dbmigrate scripts.

Issue while using docker image

I'm getting the below error when I try to use any docker image in micro pcf. The usual cf push works fine though with downloading for build packs but when I try to pull docker image from the docker hub it fails.

2016-01-24T21:49:04.48+0530 [API/0]      OUT Created app with guid 02afa31f-fa08-42c4-8b15-353b3a0527d3
2016-01-24T21:49:04.79+0530 [API/0]      OUT Updated app with guid 02afa31f-fa08-42c4-8b15-353b3a0527d3 ({"route"=>"8272d5ad-c1be-4623-bf04-686172c4faea"})
2016-01-24T21:49:05.15+0530 [API/0]      OUT Updated app with guid 02afa31f-fa08-42c4-8b15-353b3a0527d3 ({"state"=>"STARTED"})
2016-01-24T21:49:05.18+0530 [STG/0]      OUT Creating container
2016-01-24T21:49:06.17+0530 [STG/0]      OUT Successfully created container
2016-01-24T21:49:06.39+0530 [STG/0]      OUT Staging...
2016-01-24T21:49:06.43+0530 [STG/0]      OUT Staging process started ...
2016-01-24T21:49:11.47+0530 [STG/0]      ERR Failed to talk to docker registry: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection
2016-01-24T21:49:16.46+0530 [STG/0]      ERR Failed to talk to docker registry: Get https://registry-1.docker.io/v2/: read tcp 52.7.137.51:443: use of closed network connection
2016-01-24T21:49:16.46+0530 [STG/0]      ERR Staging process failed: Exit trace for group:
2016-01-24T21:49:16.46+0530 [STG/0]      ERR builder exited with error: failed to fetch metadata from [training/webapp] with tag [latest] and insecure registries [] due to Get https://registry-1.docker.io/v2/: read tcp 52.7.137.51:443: use of closed network connection
2016-01-24T21:49:16.46+0530 [STG/0]      OUT Exit status 2
2016-01-24T21:49:16.47+0530 [STG/0]      ERR Staging Failed: Exited with status 2
2016-01-24T21:49:16.54+0530 [API/0]      ERR Failed to stage application: staging failed

More FAQs

Please add to the FAQ https://github.com/pivotal-cf/micropcf/blob/master/FAQ.md#general-questions

Why is this called micropcf rather than microcf?
Why is this in https://github.com/pivotal-cf rather than https://github.com/cloudfoundry-incubator?
If it is packaging Pivotal Cloud Foundry (https://github.com/pivotal-cf/micropcf/blob/master/FAQ.md#if-my-application-runs-on-micropcf-will-it-run-on-pcf) rather than OSS Cloud Foundry, what are the differences? Is the Pivotal Web Console app included? What are the licensing restrictions for running micropcf vs running Cloud Foundry Foundation's Apache codebases?

Error setting API endpoint

I got MicroPcf up and running. I can ssh into the instance and run the cf command fine but from my host machine it fails. Here is the error I am getting:

xxxx@kubuntu-laptop:/tmp$ export MICROPCF_IP=10.0.2.15
xxxx@kubuntu-laptop:/tmp$ cf api api.local.micropcf.io --skip-ssl-validation
Setting api endpoint to api.local.micropcf.io...
FAILED
Error performing request: Get http://api.local.micropcf.io/v2/info: dial tcp 192.168.11.11:80: i/o timeout

I am running VirtualBox 5.0.14 on Kubuntu 15.10. The IP address in virtual box defaulted to 10.0.2.15 so I set the variable as described.

could not figure out where it was getting 192.168.11.11.

I also tried:
cf api 10.0.2.15 --skip-ssl-validation

but get no route to host error.

Any help appreciated.
Thanks Ed.

Setting up the micropcf development env, git clone failed

Following the guide micropcf/DEVELOP.md, git clone operation fails with error message

Submodule 'assets/rabbit-example-app' (https://github.com/pivotal-cf/rabbit-example-app.git) registered for path 'assets/rabbit-example-app'
Cloning into 'assets/rabbit-example-app'...
remote: Counting objects: 115, done.
remote: Total 115 (delta 0), reused 0 (delta 0), pack-reused 115
Receiving objects: 100% (115/115), 1.90 MiB | 1.72 MiB/s, done.
Resolving deltas: 100% (43/43), done.
Checking connectivity... done.
Submodule path 'test/src/github.com/pivotal-cf/cf-rabbitmq-smoke-tests/assets/rabbit-example-app': checked out '55b12318c9fb9677e06e10255b84c1e3da13553f'
Failed to recurse into submodule path 'releases/cf-mysql-release'
Unable to checkout 'dc571470ca621d3e919e47fb9538277452b2b1ab' in submodule path 'test/src/github.com/mdelillo/cf-mysql-acceptance-tests'

Navigating directly to github.com/mdelillo/cf-mysql-acceptance-tests I can see the module but not sure why is it failing to checkout

Also noticed another error message towards the beginning, but this one doesn't interrupt the git clone operation

remote: Repository not found.
fatal: repository 'https://github.com/fraenkel/candiedyaml/' not found
Clone of 'https://github.com/fraenkel/candiedyaml' into submodule path 'src/github.com/fraenkel/candiedyaml' failed

Thanks

No service offerings found

When I use cf marketplace i get No service offerings found. Same issue with cf services.

I expect to have rabbitmq, mysql and redis running - the processes for this services are all running and the ports are also opened / working.

The only problem I see i that pcfdev is not offering this as a service. Any idea?

I'm using version 0.15.0 from pivotal.io