My use case is to share the host’s /var/run/docker.sock with the container, but there are definitely other use cases such as not wanting to copy a huge host directory into the image or sharing container output through a shared folder.
-Brian
My use case is to share the host’s /var/run/docker.sock with the container, but there are definitely other use cases such as not wanting to copy a huge host directory into the image or sharing container output through a shared folder.
-Brian
@bmuchmore This is a useful feature indeed. We’ll add it and let you know when it’s released.
That is great! Thank you.
-Brian
Thanks for giving us shinyproxy. Lovin’ it!
I believe this feature will be key for one of our shiny applications. The use case is that our app uses data that’s from a dynamic source and processes it substantially. As the download and processing takes >20s, the data is updated in the background every 30mins.
Thus, we cannot prepare the data when the container is started or store it in the image. I believe we need to be able to access the data on the host but am happy to hear other suggestions.
Thanks
Hi @bmuchmore and @msenn,
Early Christmas present
http://www.shinyproxy.io/downloads/
http://www.shinyproxy.io/configuration/#apps
Best,
Tobias