Port "collision avoidance" when creating stacks.

[danielrosehill]

Is your feature request related to a problem? Please describe

Yes, the somewhat common problem of deploying containers onto crowded Docker networks and it becoming a challenge to remember port assignments.

Describe the solution you'd like

It would be very cool if when you paste a docker-compose in the stack deployment window the system could warn if the stack you're attempting to deploy would deploy onto occupied ports and if so it might even suggest alternatives. I guess this would probably require some kind of AI integration or enhancement. And it would also mean that the system would need to keep a running tally of all the ports that are assigned, although I imagine this probably already happens under the hood.

Describe alternatives you've considered

There are workarounds like using reverse proxies and routing to containers by name, but sometimes it's easier just to customize a boilerplate docker-compose than to try tinker with the networking.

Additional context

No response

[Nick-Portainer]

Hi @danielrosehill Thanks for this, I am raising this as a feature request but I will not be able to give any ETA at this stage.