Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Names of containers are not resolved #2294

Closed
shadjiiski opened this issue Sep 10, 2016 · 2 comments
Closed

Names of containers are not resolved #2294

shadjiiski opened this issue Sep 10, 2016 · 2 comments
Assignees
Labels
impact/test/integration Requires creation of or changes to an integration test kind/defect Behavior that is inconsistent with what's intended

Comments

@shadjiiski
Copy link

I have been following the Simple Bridge Network example. I could not ping one container from another using its name (or even its hostname).

VIC Version: JFrog Bintray builds 4677, 4715 and 0.5.5

Code

# Create a bridge network
docker --tls network create -d bridge test

# The create two alpine containers and attach them to the created network
docker --tls run -itd --name alp1 --network test alpine sh
docker --tls run -itd --name alp2 --network test alpine sh

# Attach to alp1 and ping alp2 by its name (fails)
docker --tls attach alp1
/ # ping alp2
ping: bad address 'alp2'

# While still attached to alp1, try to ping itself by name (suceeds)
/ # ping alp1
PING alp1 (127.0.1.1): 56 data bytes
64 bytes from 127.0.1.1: seq=0 ttl=64 time=0.200 ms

# Try to ping alp2 by its hostname (I got this by running hostname command in alp2 container) (also fails)
/ # ping 1bdeecd10595
ping: bad address '1bdeecd10595'

# Detach from alp1 and attach to alp2. Try the same things, you will get the same results

Expected behavior:
Container's name should have been resolved and I should have been able to ping alp2 from alp1 (and vice versa) by using ping alp2

Actual behavior:
Containers's names were not resolved and thus ping attempts were unsuccessful.

Note:
This is a simplified minimalist example. I have come across to this issue while trying to get a wordpress container to connect to a mysql container on mysql:3306.

@mdubya66
Copy link
Contributor

Required by Admiral

@mdubya66 mdubya66 added the impact/test/integration Requires creation of or changes to an integration test label Sep 19, 2016
@mhagen-vmware mhagen-vmware added the impact/doc/note Requires creation of or changes to an official release note label Sep 20, 2016
@stuclem
Copy link
Contributor

stuclem commented Nov 7, 2016

This is fixed. Removing kind/note.

@shadjiiski shadjiiski removed the impact/doc/note Requires creation of or changes to an official release note label Nov 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/test/integration Requires creation of or changes to an integration test kind/defect Behavior that is inconsistent with what's intended
Projects
None yet
Development

No branches or pull requests

5 participants