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

scope probe connects to localhost & prod even when given explicit hostnames #1566

Closed
jml opened this issue Jun 8, 2016 · 0 comments
Closed
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Milestone

Comments

@jml
Copy link
Contributor

jml commented Jun 8, 2016

Reproduce:

  • run ./scope launch --service-token $TOKEN $IP_ADDRESS:$PORT
  • observe the output container ID
  • run docker logs -f $CONTAINER_ID

Observed:

Logs contain:

 <probe> INFO: 2016/06/08 12:55:40.983088 publishing to: localhost:4040, $IP_ADDRESS:$PORT, scope.weave.works:443

and then following there are "connection refused" errors for connecting to 127.0.0.1.

Expected:

I would have expected the probe to connect only to the IP address I specified, and not to localhost or scope.weave.works.

@2opremio 2opremio added the bug Broken end user or developer functionality; not working as the developers intended it label Jun 15, 2016
@2opremio 2opremio added this to the 0.16.0 milestone Jun 15, 2016
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

2 participants