Configuring Pivotal Platform Dev

Page last updated:

Note: If you are using Pivotal Platform Dev v0.30 or earlier, see Configuring Pivotal Platform Dev (Legacy).

Pivotal Platform Dev supports several different configurations. This topic describes how to start Pivotal Platform Dev with specific memory usage, core count usage, custom startup .iso and .tgz files, and Pivotal Platform services, among others. It also describes ease-of-use functionality, including automatically targeting Pivotal Platform Dev and trusting Pivotal Platform Dev certificates.

Configure Pivotal Platform Dev

The cf dev start command supports the following configuration-specific flags at startup:

flag description
-c NUMBER-OF-CORES Specify the number of processor cores used by VM. Default: 4.
-f FILEPATH Specify the path to the .dev file containing the bosh and cf bits to start with.
-m MEMORY-IN-MB Specify memory to allocate for VM. Default: 8 GB.
-r REGISTRY-1,REGISTRY-2,... Specify Docker registries for Pivotal Platform Dev to use without SSL validation. Use host:port format.
-s SERVICE-1,SERVICE-2,... Specify services to start with. Options: scs, redis, mysql, rabbitmq, all. Default: none. You can deploy services ad hoc after start.

Insecure Docker Registries

You can push apps to Pivotal Platform Dev from Docker images.

By default, these images must be hosted on Docker Hub. Use the -r flag to specify Docker registries that Pivotal Platform Dev should allow you to push from, even if those registries do not have valid SSL certificates.

For example, to start Pivotal Platform Dev and push an app using an existing insecure Docker registry on your host running on port 5000, run:

cf dev start -r host.pcfdev.io:5000
cf dev target
cf push -o host.pcfdev.io:5000/repository/image