DOCKER-724: support `docker network connect`

Details

Issue Type:Bug
Priority:4 - Normal
Status:Open
Created at:2016-03-03T22:36:52.000Z
Updated at:2018-06-26T06:49:19.267Z

People

Created by:Matthew Smillie [X]
Reported by:Matthew Smillie [X]
Assigned to:Todd Whiteman

Related Issues

Description

Add/remove nics to docker containers.

Comments

Comment by Todd Whiteman
Created at 2017-11-06T19:55:45.410Z

@angela.fong, @casey.bisson "docker network connect --alias foo" (and "docker run --network N --network-alias foo" ) allows adding an alias/DNS name that is only visible to other containers on the same network. So this is like CNS, but the container name is restricted by network.

c.f. https://docs.docker.com/engine/reference/commandline/network_connect/#create-a-network-alias-for-a-container

In order to support this, CNS would need to be updated. I would suspect that we would add a DNS name resolver to the container that uses the network uuid instead of the account uuid, e.g. foo.${NETWORK_UUID}.us-east-1.joyent.us, then when a container is looking up the alias name, CNS can verify if that container is connected to the given network and return the DNS IP address as warranted.

Do we want to support this feature, or alternatively do we just want to add the alias name to all networks (i.e. like a regular container CNS name)?