[Feedback Captured] Docker network creation/management support

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.

2 Likes

As there are a range of usability and functional improvement items for apps in the feature requests, we are gathering these together into a common item on our roadmap. This request has been captured and is included in that roadmap item.

What this means:

  • Our product team will now evaluate technical feasibility, resource requirements, and alignment with our product strategy
  • This request is now closed for voting, and your votes have been released back to use on other requests
  • We’ll conduct a thorough analysis to determine if and how this feature might be implemented
  • Please note that transfer to the roadmap doesn’t guarantee implementation - some features may not proceed based on our assessment findings, however we will update this thread once a decision has been made.

Thank you to everyone who voted and contributed to the discussion. Your input has been invaluable in helping us understand the community’s needs and use cases for this feature.

1 Like