Configuring PCF Dev

Page last updated:

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

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

Configure PCF 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/file 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 registry1,registry2,... Specify Docker registries for PCF Dev to use without SSL validation. Use host:port format.
-s service1,service2,... Specify services to start with. Accepts -scs,redis,mysql,rabbitmq,all. Default: none. You can deploy services ad hoc after start.

Insecure Docker Registries

You can push applications to PCF Dev from Docker images.

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

The following example shows how to start PCF Dev and push an app using an existing insecure Docker registry on your host running on port 5000:

$ cf dev start -r host.pcfdev.io:5000
...
$ cf dev target
Successfully logged in to api.local.pcfdev.io as user.
$ cf push -o host.pcfdev.io:5000/repository/image
Create a pull request or raise an issue on the source for this page in GitHub