Hello!

I have been attempting to run a persistent Tomcat webserver/webapp inside of a 
Docker container generated by Aurora, all inside Vagrant. The docker image is 
preloaded with the Tomcat software and webapp, such that it only requires a run 
command in order to start the Tomcat webapp. I wanted to be able to see my 
webapp in browser so I attempted to publish the Docker port onto a port on the 
Vagrant environment, using the following code as part of the Service 
description in the .aurora:


container = Docker(image = 'tomcatimage', parameters = [Parameter(name = 
'publish', value = '8080:8080')])


The docker image executes the Dockerfile command "EXPOSE 8080", which I can 
safely assume accomplishes what it promises. The publish parameter is used to 
map the 8080 port inside docker to the host port 8080. So, the webapp should be 
visible at http:\\localhost:8080 , where localhost is designated by the 
Vagrantfile.


However, this does not successfully publish onto the 8080 host port.



When I run the docker container independently of Aurora, without any input 
parameters, and type 'docker ps' into the CLI, the output shows "8080/tcp" 
under "PORTS".


 If I run the container with the flag "-p 8080:8080", the 'docker ps' output 
shows "0.0.0.0:8080->8080/tcp": this mapping results in a webpage I can access 
by navigating a browser to http://192.168.33.7:8080 , with 
192.168.33.7<http://192.168.33.7:8080>  being the localhost defined in the 
Vagrantfile.


However, when aurora generates the docker container (using the same docker 
image), it has nothing at all listed in the "PORTS" output of 'docker ps', and 
cannot be accessed by navigating to a web page.


Has anyone experienced this (fairly specific) problem? Suggestions? Any 
additional details required to diagnose?


Thanks!

Reply via email to