Closed massaox closed 3 years ago
Hi @massaox
Since you are using the Docker image of ShinyProxy 2.5.0 , the configuration file should not be mounted under /etc/shinyproxy/application.yml
, but under `/opt/shinyproxy/application.yml'. This changed since the docker image of 2.5.0. This is reflected in the latest versions of the ShinyProxy operator (at least openanalytics/shinyproxy-operator-snapshot:0.0.1-SNAPSHOT-20210302.095930) . Unfortunately this was not yet updated in the example deployments.
I'm re-writing the example deployments as we speak (to provide more re-usable examples). So I'll make sure to update the image version.
Please let me know if this fixes your issue.
Note you can use openanalytics/shinyproxy-operator-snapshot:latest
as image for the operator, to ensure you are always using the latest version (we are using that tag in the new docs now as well).
HI @LEDfan,
Thank you very much for the quick response. You were absolutely right. Once I changed the image of the operator to run the latest one it worked flawlessly. The configMap was indeed mounted under /opt/shinyproxy/application.yaml
and no further configuration was need.
I will go ahead and close down this issue. Keep up the good work!
Hi,
I have followed the instructions to deploy the shinyproxy operator in a clustered manner (with some slight modification) but I was not able to get the shinyproxy Pod to create the r-apps applications. At least it seems to operator is doings its job e.g creating the shinyproxy Pod, the configMap, Service and Skipper ingress. I have tested using Minikube version 1.20 and GKE 1.18 and 1.20, all approaches returning the same error. Below you can see the full error output when I tried to instantiate the "hello" application:
Looking at the logs from the shinyproxy Pod I was able to retrieve also the following entries:
I could not figure it out where the
unix://localhost:80
is coming from. All the manifest deployed are the ones under theclustered
directory in the repo, the only change I made was on the shinyproxy manifest that looks like the following:I "exec'ed" into the shinyproxy Pod and could confirm the shinyproxy container was using all the info above as it was on the file
/etc/shinyproxy/application.yml'. So I am not sure if there are any further parameters that need to be passed under
proxy.kubernetes` in order to work or there is a bug somewhere, I had tried adding the following but to no avail:Any insights are appreciated ;)