Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add anonymous container alias to service record on attachable network #1651
Signed-off-by: Alessandro Boch email@example.com
Mar 2, 2017
2 checks passed
I confirm it now works when using only one network, but not when using multiple nets and later connecting individual containers from the stack to some not previously connected networks (docker network connect --alias)
Tested with Docker version 17.06.2-ce, build cec0b72
To reproduce :
Every thing looks fine so far :
But both the manually added alias and the ct_id are not resolved by the embedded DNS
I've been bitten by the same problem right this second.
My use case, is to have a service listening on 1 port (https server) to be able to redirect to 2 subnets.
so instead of using aliases (which don't work currently) maybe by having a TLD called dev_dashboard_default, we could redirect to grafana.dev_dashboard_default and the same for the prod for example.