You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm noticing many users (including myself) being confused by a quirk of ShinyProxy: if an image doesn't exist on the docker host, ShinyProxy refuses to boot it. This issue isn't reported here, but rather, on the configuration examples provided by your example repo:
This missing feature is non-obvious to newcomers, and makes the shinyproxy docker container unable to stand on it's own (it requires that it's host contain more than docker, namely, all the docker images it serves). Is there an obvious reason this requirement exists, or could docker pull be invoked if an image isn't found on the host? This missing feature makes deploying shinyproxy on docker orchestrators difficult, where admins shouldn't have to care about host requirements, and where automated janitors might sweep away "unused" images shinyproxy relies on, breaking the site.
The text was updated successfully, but these errors were encountered:
To users trying out the example files it may not be immediately obvious that the Docker image must be available on the host, and the error message is very generic. This seems to be an issue with other users that test ShinyProxy, see also: openanalytics/shinyproxy#82
Greetings,
I'm noticing many users (including myself) being confused by a quirk of ShinyProxy: if an image doesn't exist on the docker host, ShinyProxy refuses to boot it. This issue isn't reported here, but rather, on the configuration examples provided by your example repo:
openanalytics/shinyproxy-config-examples#4
openanalytics/shinyproxy-config-examples#2
This missing feature is non-obvious to newcomers, and makes the shinyproxy docker container unable to stand on it's own (it requires that it's host contain more than docker, namely, all the docker images it serves). Is there an obvious reason this requirement exists, or could
docker pull
be invoked if an image isn't found on the host? This missing feature makes deploying shinyproxy on docker orchestrators difficult, where admins shouldn't have to care about host requirements, and where automated janitors might sweep away "unused" images shinyproxy relies on, breaking the site.The text was updated successfully, but these errors were encountered: