# Container failed to start issue - containerised ShinyProxy

**URL:** <https://support.openanalytics.eu/t/container-failed-to-start-issue-containerised-shinyproxy/942>\
**Category:** ShinyProxy\
**Created:** [February 8, 2019, 2:57pm UTC](https://support.openanalytics.eu/t/container-failed-to-start-issue-containerised-shinyproxy/942 "2019-02-08T14:57:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![t.bowling](https://support.openanalytics.eu/letter_avatar_proxy/v4/letter/t/ed655f/32.png) [@t.bowling](https://support.openanalytics.eu/u/t.bowling)\
**Post date:** [February 8, 2019, 2:57pm UTC](https://support.openanalytics.eu/t/container-failed-to-start-issue-containerised-shinyproxy/942/1 "2019-02-08T14:57:56Z")

</div>

Hi,

I’m just getting started trying to use ShinyProxy to host a shiny app that I’ve built. I’m trying to do so running shiny proxy inside a docker container as per example set up 02 (in fact I’m deploying it from that example with a few tweaks made to the application.yml file.

The container image for the app itself builds ok and I can access it directly when spun up outside of shiny proxy.

I created the docker network and the application.yml file looks like this  
 ![image](https://support.openanalytics.eu/uploads/default/original/1X/290a928cc5d7f865ab8ad52a8f38f1e96b3aa013.png)

I’ve checked for firewall issues as per the troubleshooting guide and that doesn’t appear to be the problem. Any suggestions would be much appreciated

---

<div class="post-metadata">

**Author:** ![ana](https://support.openanalytics.eu/letter_avatar_proxy/v4/letter/a/a6a055/32.png) [@ana](https://support.openanalytics.eu/u/ana)\
**Post date:** [February 11, 2019, 9:15am UTC](https://support.openanalytics.eu/t/container-failed-to-start-issue-containerised-shinyproxy/942/2 "2019-02-11T09:15:05Z")

</div>

Hi,

Have you tried authentication: simple?  
Did you do this?

Create a docker network that ShinyProxy will use to communicate with the Shiny containers.

docker network create sp-example-net

Build the ShinyProxy image:

docker build . -t shinyproxy-example

Run the following command to launch the ShinyProxy container:

docker run -d -v /var/run/docker.sock:/var/run/docker.sock --net sp-example-net -p 8090:8090 shinyproxy-example

You can try to see the log:  
docker logs [OPTIONS] CONTAINER

Kind regards,  
Ana

---

<div class="post-metadata">

**Author:** ![t.bowling](https://support.openanalytics.eu/letter_avatar_proxy/v4/letter/t/ed655f/32.png) [@t.bowling](https://support.openanalytics.eu/u/t.bowling)\
**Post date:** [February 11, 2019, 9:48am UTC](https://support.openanalytics.eu/t/container-failed-to-start-issue-containerised-shinyproxy/942/3 "2019-02-11T09:48:40Z")

</div>

Thanks Ana, I was missing the -v and the --net specification in the docker run command. I naively assumed that it would pick that information up from the application.yml.

All seems to be working smoothly now.

Cheers

Tom
