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 launch stopped working agains latest Docker for Mac (beta9) #1411

Closed
errordeveloper opened this issue Apr 29, 2016 · 0 comments · Fixed by #1414
Closed

scope launch stopped working agains latest Docker for Mac (beta9) #1411

errordeveloper opened this issue Apr 29, 2016 · 0 comments · Fixed by #1414
Assignees
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Milestone

Comments

@errordeveloper
Copy link
Contributor

errordeveloper commented Apr 29, 2016

The new beta9 release has only so called "VPN-compatible" mode. In this mode container ports are accessible on localhost, but no access to host network is provided (as it bypasses Docker port publishing machinery).

0 %> ~/Code/scope/scope launch
ec952734f2df481f8a220024a79a5c712e2d45aa5476a762ee17fa49d95c335d
Weave Scope is reachable at the following URL(s):
  * http://192.168.65.2:4040/
  * http://172.19.0.1:4040/

0 %> curl http://192.168.65.2:4040/
^C

1 %> curl http://172.19.0.1:4040/
^C

1 %> curl http://localhost:4040/
curl: (7) Failed to connect to localhost port 4040: Connection refused

7 %> ping -c1 docker.local
ping: cannot resolve docker.local: Unknown host

68 %> docker run -ti --net=host centos:7 curl localhost:4040
<!doctype html>
<html class="no-js">
  <head>
    <meta charset="utf-8">
    <title>Weave Scope</title>
    <meta name="description" content="">
    <meta name="viewport" content="width=device-width, initial-scale=1">
  <link href="style-app.css?22d50f02be7313bbc64a" rel="stylesheet"></head>
  <body>
    <!--[if lt IE 10]>
      <p class="browsehappy">You are using an <strong>outdated</strong> browser. Please <a href="http://browsehappy.com/">upgrade your browser</a> to improve your experience.</p>
    <![endif]-->
    <div class="wrap">
      <div id="app"></div>
    </div>
  <script src="vendors.js?22d50f02be7313bbc64a"></script><script src="app.js?22d50f02be7313bbc64a"></script></body>
</html>

Yet, the app is fully accessible inside of the host. My assumption is that splitting app and probe and running the app in it's own network namespace should work, but I haven't tested it yet.

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

Successfully merging a pull request may close this issue.

2 participants