Hi Pankaj, With dockerizing each component has to be a docker container. Ex: I am sure you can find a zookeeper docker image in docker hub, same thing to other third party components. We should run airavata isolate in one container which should be able to connect to other containers. You need to do -p hostport:container port to export desired port to the outside world (Ex:port 80) if you want to communicate internally (If those components are docker containers, IMO all of these components should be containerized) you have to link containers when you run the image with --link which will link containers.
Regards Lahiru On Wed, Jun 17, 2015 at 8:45 AM, Pankaj Saha <[email protected]> wrote: > Once a docker container is running how can the host system be able to > communicate to the running image? > > I believe there is a command EXPOSE <port number> to make one application > exposed to the host through the mentioned port. In airavata we need several > applications (rabbiMQ,Zookeeper etc) to run on different ports inside their > container and should be able to communicate. > > Currently airavata-service.sh is the one point which invokes all the > rquired applications and keep them alive on specific ports. > > After dockerising how can that be possible? Do we need to change the > airavata-service.sh file to be changed? > > Thanks > Pankaj >
