I’m new to shinyproxy and am slowly trying to build myself up to having a containerised environment that will allow me to serve my app to numerous people with various levels of permission.
As it stands I’ve been able to build a sample repo that works when I execute the following (from the root directory of the repo):
-
sudo docker build -t thedatacollective/basic_proxy ./shinyproxy# to build the shinyproxy image -
sudo docker build -t thedatacollective/basic_shiny ./apps# to build the app that gets served by shinyproxy -
sudo docker run -d -v /var/run/docker.sock:/var/run/docker.sock --net tdc-net -p 8080:8080 thedatacollective/basic_proxy# to launch the proxy
I can then navigate to http://127.0.0.1:8080 and I am served with the login screen and with correct credentials the app will load correctly.
I am now trying to level up so I can get this working via docker-compose, which is causing me problems. At the moment when I run docker-compose up --build things build and I’m served with the shinyproxy login screen, however I eventually get a error 500 telling me the container did not respond in time.
I have tested that the application container works independently of shinyproxy. I have tested it using docker run and it does work those ways, however there must be something wrong in my understanding of docker-compose that is causing me grief.
When I’ve logged in I can see the application container exists, however the logs for shiny proxy tell me that the Container unresponsive, trying again (2/10): http://9907791e28a4:3838
I’d really appreciate any guidance available. I’ve done my best to look at other examples and repo’s but must just be missing something in my understanding.
Cheers
Dan