CODEWITHSUNDEEP
dockerdocker-composecloud-foundrypcf
Rishabh
Rishabh

Reputation: 43

How docker container can communicate in PCF

I have multiple docker containers. In local they talk to each other using network and compose.yml. I have pushed my containers to PCF only i don't know how to make them talk to each other. Can anyone help me out??

Upvotes: 0

Views: 1050

Answers (1)

Daniel Mikusa
Daniel Mikusa

Reputation: 15051

My understanding is that you would utilize Cloud Foundry's container to container networking to do this.

https://docs.cloudfoundry.org/concepts/understand-cf-networking.html

By default, no connections are allowed between containers but you can use the cf cli to allow connections on specific ports between your applications. Your applications just need to be configured to start and listen on the ports that you allow.

While it's not docker specific, there's a good example here.

https://github.com/cloudfoundry/cf-networking-examples/blob/master/docs/c2c-no-service-discovery.md

Using docker should be minimally different. You'll obviously need to create your own docker images and make sure that those are going to listen on the correct ports, otherwise it's just an adjustment to how you push the application (i.e. pass the docker image name to cf push). The cf add-network-policy commands should be the same.

Hope that helps!

** UPDATE **

If you are looking for docker-compose like behavior, kind of a run one command and deploy multiple apps, you can achieve this with cf push and a manifest.yml file.

The manifest.yml file allows you to define multiple applications. Thus you can use it to deploy a series of applications that work together, like you often see with docker-compose.

https://docs.cloudfoundry.org/devguide/deploy-apps/manifest-attributes.html

You have quite a bit of flexibility with manifest.yml, you can deploy buildpack based apps or docker image based apps. You can configure routes, bound services, health checks, memory/disk quotas, and if you're on a new enough version, even processes and sidecars. That said, it can't do 100% of what you can with the cf cli, for example you cannot control the above mentioned network policy using a manifest.yml. If you need to control something not exposed through manifest.yml, the other option would be to script the deployment.

Upvotes: 3

Related Questions