Problem/Justification
Currently, built-in apps only use their own networks (ix-[appname]-default), host, bridge, or none. Docker natively supports container network creation and management, and even allows for connection to multiple networks. The only way to do this on TNCE at the moment is to use a third party management software (Dockage or Portainer), the CLI, or converting to a custom app and changing the compose file. Also, if you add an ix-app to a docker network, it disconnects from that network every time you redeploy the app, which leads to manual network connection every time.
The reason Docker network management is useful is because simply allowing all containers to communicate with each other is not necessary nor secure. For example, my OmniTools doesn’t really need nor should have access to my Authentik database.
Impact
This will allow users to not have to use workarounds to manage their Docker networks, and also allow a higher level of security for reasons I mentioned above.
User Story
Add this to the “networking” tab, and/or apart of the app settings/deployment screen.