[FR] containers join the same network as shinyproxy itself by default

[shrektan]

When shinyproxy is running in a docker container and docker.internal-networking is set to true, would it be possible to set the spec.id.container-network as the same as the shinyproxy, automatically?

I request this feature is because when running in a docker-compose, the network is usually created by docker itself with the name (directory-name)_default. So everytime I changed the directory, I have to reset all the spec.id.container-network again. It's not good. And it's tedious especially when testing...

Moreover, docker-compose may create other network name if there exists the default one...

Thanks.

[nuno-agostinho]

Any news on this feature? I also use shinyproxy in docker-compose and would prefer if I did not have to set a container-network: "${proxy.docker.container-network}" to every app.

Alternatively, a way to set the container-network for all apps would be good too for my use case.

[LEDfan]

Hi, this issue is not yet solved, but we will consider it for the upcoming releases. I'll keep you informed when we want to implement this.