
“If you’ve ever attempted to run too many containers on the same machine, you may have encountered failed deployments because multiple services tried accessing the same port. Fortunately, DCM sidesteps that issue by checking for port conflicts in your multi-container Compose files. Going back to our network stack example, Nginx and Pi-hole both use ports 80 and 443 on the host. If you try to deploy these services with the same Compose files, DCM detects the port conflicts and assigns different numbers to the second container.”
With over 40 to 50 containers running on one of my servers I constantly run into that ports clashing issue (when ports are exposed to the host machine). This tool does look quite interesting as well as how it handles volume mappings.
It also makes me realise how Portainer really needs to take a few steps forward with regard to better stack editing.
I’m going to be looking a bit deeper into this app. It looks like it will work in tandem with Portainer too. Basically DCM will help you create a clean and functional docker-compose file to paste into Portainer.
See xda-developers.com/this-docker… or the project site at github.com/ajnart/dcm
#Blog, #docker, #selfhosting, #technology

