Troubleshoot "Failed to start app"

1

I’m getting failures to start an app after logging into ShinyProxy. I’m wondering how I can troubleshoot this. Can I run ShinyProxy interactively and open my app from within?

I know the problem is not with the app image as it works fine on its own. I’m wondering if I’m having issues passing environment variables using the application.yaml’s container-env (below) or container-env-file (not shown) parameters. This is my application.yaml:

proxy:
  title: Interactive Data Applications
  logo-url: https://www.openanalytics.eu/shinyproxy/logo.png
  port: 8080
  authentication: simple
  admin-groups: admins
  users:
  - name: jack
    password: password
    groups: admins
  - name: jeff
    password: password
  docker:
      internal-networking: true
  specs:
  - id: 01_cso-maint
    display-name: My App
    container-cmd: ["R", "-e", "shiny::runApp('/home/app')"]
    container-image: cso-maint
    container-network: shinyproxy
    # container-env-file: /tmp/envs/.env.list
    container-env:
      POSTGRES_USER: ${POSTGRES_USER}
      POSTGRES_PASS: ${POSTGRES_PASS}
    container-volumes: ["/var/log/shinylogs:/home/app"]
logging:
  file:
    shinyproxy.log

My run command

docker run -d \
	--name shinyproxy \
	--env-file /home/asadowsk/envs/.env.list \
	-v /var/run/docker.sock:/var/run/docker.sock:ro \
	--group-add $(getent group docker | cut -d: -f3) \
	--net shinyproxy \
	-p 8080:8080 shinyproxy
2

Hi

First of all, it makes sense to look at the shinyproxy logs, to see what is going on. Feel free to post your logs so we can have a look.

In addition, it can be useful to use the docker cli to debug. E.g. you can use docker ps to list the docker contains, docker logs <id> and docker exec <id> to debug a container.

1 Like