hop of those help? The problem was the docker container exposed two ports, one on which the healthcheck endpoint was accessible and another that could be used for debugging. PCF always chose to try to run the health check against the debug port. There is no way to specify, for PCF, a port for the health check to run against. It chooses among the exposed ports and for a reason I don't know always chose the the one intended for debugging.
Hope that helps To answer your specific question about whether you will need to make changes to your Docker image or not, here's the relevant info. Currently there is no support for mounting volumes or linking containers, but projects to support these use cases are actively in flight, so if your docker run workflow normally involves that you will have to wait. There is only support for v2 Docker registries, so if your image repository is in a Docker registry with an older API, it won't work. There is no support for private repositories (that is, repositories that require a username and password to access the image in the registry). You can, however, provide your own custom registry and make it only accessible to your CF backend, and then push your image as a public repo to that custom registry.
Nginx.conf for angularjs application deployed on Pivotal Cloud Foundry