This “binding” is similar to port forwarding. Docker by default runs these containers on a separate network and each of those containers have an IP address (local, accessible only inside the host machine) and run their own networking stack.
Once the port binding is complete if we access -> ''<nowiki>http://192.168.56.105:35001</nowiki> '' we should get the web interface of App1 and so on. But for our users we want the app to be reachable at app1.amahi.net. So earlier the hda used to create a virtual host file for each app which used to run the relevant app server based on the url. For container apps, the present approach does this:
The apache running on host reverse proxies all requests coming on ''<nowiki>http://app1.amahi.net</nowiki> '' to ''<nowiki>http://localhost:35001</nowiki> '' , This way for the user the url is ''<nowiki>http://app1.amahi.net</nowiki> '' and they can still access the web interface of the app.
==How the app installation works?==