Network aliases created with full container name & not short name

[skelethan]

Per https://github.com/docker/compose/blob/0409b287ad3ede39282c199d611456aab15dca71/docs/networking.md

However, what I am seeing is that the aliases are created with the full container name from compose e.g. context_web_1

This eliminates the benefit of consistent aliases, as compose will dynamically assign network alias depending on number of containers & where they are run from.

My simple test below.

[dnephin]

I'm able to reproduce this.

cc @aanand, @mavenugo

According to #1676 (comment) the container is supposed to join the network using the hostname, but that is not what's happening with docker engine 1.9.0-rc2.

The hostname is correctly set to the service name (ex: "web"), but it's joining the network as "project_web_1" (according to the /etc/hosts in other containers on the network). This is what I see:

172.18.0.2      networking_other_1
172.18.0.2      networking_other_1.networking
172.18.0.3      networking_web_1
172.18.0.3      networking_web_1.networking

Did this change? Do we need to change something on the compose side?

[dnephin]

@skelethan thanks for reporting this. Unfortunately we weren't able to fix this for the current release so we've updated our documentation to match what is supported right now (the container joins the networking using the container name).

In the next release we'll have support for aliases which should support a much nicer short names.

[Teudimundo]

Is there any workaround that could be used? Since addresses with _ are not valid FQDN this bug can cause some pain.

[dnephin]

@Teudimundo yup, the docs mention that you can set a custom container name with container_name:.

[Teudimundo]

Thank you, I missed that.

[pwaller]

Is there a workaround which doesn't involve setting the container name? I need to run multiple copies of the project at once with different project names, in a CI runner.