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

Missing edge between containers in host networking namespace #1258

Closed
2opremio opened this issue Apr 11, 2016 · 3 comments
Closed

Missing edge between containers in host networking namespace #1258

2opremio opened this issue Apr 11, 2016 · 3 comments
Labels
bug Broken end user or developer functionality; not working as the developers intended it

Comments

@2opremio
Copy link
Contributor

To reproduce, launch scope (master, without weave network) and then.

In one terminal:

docker run --net=host --rm --name=httpd python:2.7 python -m SimpleHTTPServer

In a different terminal:

docker run --net=host --rm --name=httpclient tutum/curl bash -c 'while true; do curl -s localhost:8000; sleep 1;  done'

What I see:

screen shot 2016-04-11 at 2 06 24 pm

Report: report_missing_host_connection.json.gz

What I expect: An edge between the httpd and httpclient containers.

(Changing localhost:8000 to external_interface_ip:8000 doesn't help either).

The process view doesn't wither show connected processes.

@2opremio 2opremio added the bug Broken end user or developer functionality; not working as the developers intended it label Apr 11, 2016
@2opremio 2opremio changed the title Missing connection between containers in host networking namespace Missing edge between containers in host networking namespace Apr 11, 2016
@2opremio
Copy link
Contributor Author

Related: #1162 ? (weave wasn't running here though)

@2opremio
Copy link
Contributor Author

I am also missing an edge when connecting a container in the weave network to a container in the host network using weave expose (this happened when doing a workshop at a client). I am not creating a new issue since it seems a duplicate, but let's have this in mind when fixing it.

To reproduce, in one terminal:

docker run --net=host --rm --name=httpd python:2.7 python -m SimpleHTTPServer

In another terminal:

weave launch
weave expose -h host.weave.local
eval $(weave env)
docker run --rm --name=httpclient tutum/curl bash -c 'while true; do curl -s host.weave.local:8000; sleep 1;  done'

And then launch Scope.

This is what I see:

screen shot 2016-04-11 at 2 25 42 pm

Report: report_missing_host_connection_with_weave_expose.json.gz

@2opremio
Copy link
Contributor Author

After a discussion with @tomwilkie offline, this is caused by a limitation on how we track short-lived connections.

I have created #1260 to track this instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Projects
None yet
Development

No branches or pull requests

1 participant