Stop containers instead of removing them at session end

[GorgetGuilhem]

Hi ! I'm getting a close look at ShinyProxy as it may be very useful for our business needs, and I'm actually having a question.

Our use case is pretty simple, we want to deploy several applications (VScode, JupyterLab, RStudio) for bio-informatics purposes. The users may install packages with the package manager provided in the container (apt, apk, etc), an we want these packages to be persistent.

As far as I understand and after reading the all ShinyProxy documentation, there is no way to achieve that at this time. My question is : is it already possible to stop the container at session termination instead of removing it ? If not, is it conceivable to implement a new feature that do that ? This way the user may recover the same container with the packages he already installed when he launches a new session, without having to deal with "hacky tricks" at the container level.

This is a very common use-case for us as bio-informaticians often need to work with context specific packages. A Dockerfile installing a list of pre-determined packages is then not possible as it will greatly depends of the user needs.

Thanks by advance !

[LEDfan]

Hi

This is currently not possible, containers are always stopped. I like the idea and it would be great to have such a feature. However, I think it's difficult to support it on Kubernetes, since as far as I know there is no feature to pause or stop a container.

On a plain Docker host this is could be less complex to implement.

I'll keep this issue open as a feature request.