docker-compose.ymlfrom anywhere with a web app; you may assume a
port 80is bound somewhere. However, if there's already another stack that uses it, this won't work. This seems weird to me, as I understand that you'd have to route to that specific virtual network in your swarm (hence; the reverse proxy). But I wasn't expecting it to be swarm wide when you expose a port.
test2_default(being appA and appB)
port 80assignment in there.
port 80:80, but have it randomize instead so your proxy can take
container name, so
my-container:80will have docker swarm loadbalance across all available containers under that name