shinyproxy: Shiny Proxy Can't Access Container On Host

Hey,

Here’s our docker-compose setup witih port bindings

[ec2-user@ip-10-10-0-15 oasis_build]$ docker-compose -f docker-compose.oasis.yml -f docker-compose.flamingo.ci.yml -f docker-compose.flamingo.test.yml ps
            Name                           Command               State                                       Ports
------------------------------------------------------------------------------------------------------------------------------------------------------
oasisbuild_chrome_1             /opt/bin/entry_point.sh          Up
oasisbuild_firefox_1            /opt/bin/entry_point.sh          Up
oasisbuild_flamingo_server_1    /bin/sh -c sh /var/www/oas ...   Exit 1
oasisbuild_oasis_api_server_1   /bin/sh -c sed -i -e "s/%R ...   Up       0.0.0.0:8001->80/tcp
oasisbuild_oasis_mysql_1        docker-entrypoint.sh mysqld      Up       3306/tcp
oasisbuild_oasis_rabbit_1       docker-entrypoint.sh rabbi ...   Up       15671/tcp, 0.0.0.0:15672->15672/tcp, 25672/tcp, 4369/tcp, 5671/tcp, 5672/tcp
oasisbuild_selenium_hub_1       /opt/bin/entry_point.sh          Up       0.0.0.0:4444->4444/tcp
oasisbuild_shiny_proxy_1        /bin/sh -c sed -i s/%FLAMI ...   Up       0.0.0.0:32780->8080/tcp

I checked the logs of shiny_proxy and this is the error

shiny_proxy_1       | 2018-01-05 19:09:11.720  WARN 26 --- [ XNIO-2 task-15] eu.openanalytics.services.DockerService  : Container unresponsive, trying again (2/10): http://172.18.0.1:20001

I checked the host and this is the container on 20001

[ec2-user@ip-10-10-0-15 ~]$ docker ps
CONTAINER ID        IMAGE                                    COMMAND                  CREATED             STATUS          PORTS                            NAMES
bb74f26bcc7b        coreoasis/flamingo_shiny:R_0_0_0_109     "R -e flamingo::ru..."   5 minutes ago       Up 5 minutes    0.0.0.0:20001->3838/tcp          dreamy_booth

Can you help is debug this as to why it can make the container on the host, but then thinks it can’t talk to it, when it clearly can? (we checked manually)

Many thanks, Paul