graphql-bench icon indicating copy to clipboard operation
graphql-bench copied to clipboard

Connection refused when running Docker image in Windows 10

Open jacekkk opened this issue 7 years ago • 3 comments

Hi,

I'm completely new to Docker and a bit lost as to what my problem is when trying to use this tool.

When I start the server using cat bench.yaml | docker run -i --rm -p 8050:8050 -v C:/github/graphql-bench/examples/starwars/queries.graphql hasura/graphql-bench:v0.3 I get:

==================== benchmark: query-comparison

candidate: HeroNameQuery on hero_name at http://172.17.0.1:5000/graphql Warmup: ++++++++++++++++++++ 100Req/s Duration:60s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 200Req/s Duration:60s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 300Req/s Duration:60s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 400Req/s Duration:60s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 500Req/s Duration:60s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused Benchmark: ++++++++++++++++++++ 100Req/s Duration:300s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 200Req/s Duration:300s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 300Req/s Duration:300s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 400Req/s Duration:300s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 500Req/s Duration:300s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused

candidate: HeroNameFriendsQuery on hero_name_friends at http://172.17.0.1:5000/graphql Warmup: ++++++++++++++++++++ 100Req/s Duration:60s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 200Req/s Duration:60s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 300Req/s Duration:60s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 400Req/s Duration:60s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 500Req/s Duration:60s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused Benchmark: ++++++++++++++++++++ 100Req/s Duration:300s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 200Req/s Duration:300s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 300Req/s Duration:300s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 400Req/s Duration:300s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 500Req/s Duration:300s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused

benchmark: webserver-comparison

candidate: HeroNameQuery on uwsgi at http://172.17.0.1:5001/graphql Warmup: ++++++++++++++++++++ 100Req/s Duration:60s open connections:20 unable to connect to 172.17.0.1:5001 Connection refused ++++++++++++++++++++ 200Req/s Duration:60s open connections:20 unable to connect to 172.17.0.1:5001 Connection refused ++++++++++++++++++++ 300Req/s Duration:60s open connections:20 unable to connect to 172.17.0.1:5001 Connection refused Benchmark: ++++++++++++++++++++ 100Req/s Duration:100s open connections:20 unable to connect to 172.17.0.1:5001 Connection refused ++++++++++++++++++++ 200Req/s Duration:100s open connections:20 unable to connect to 172.17.0.1:5001 Connection refused ++++++++++++++++++++ 300Req/s Duration:100s open connections:20 unable to connect to 172.17.0.1:5001 Connection refused

candidate: HeroNameQuery on dev-server at http://172.17.0.1:5000/graphql Warmup: ++++++++++++++++++++ 100Req/s Duration:60s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 200Req/s Duration:60s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 300Req/s Duration:60s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused Benchmark: ++++++++++++++++++++ 100Req/s Duration:100s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 200Req/s Duration:100s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused ++++++++++++++++++++ 300Req/s Duration:100s open connections:20 unable to connect to 172.17.0.1:5000 Connection refused

  • Serving Flask app "bench" (lazy loading)
  • Environment: production WARNING: Do not use the development server in a production environment. Use a production WSGI server instead.
  • Debug mode: off
  • Running on http://0.0.0.0:8050/ (Press CTRL+C to quit)

As you can see from the logs, it can't connect to 172.17.0.1:5000, and therefore when I open http://127.0.0.1:8050 in my browser I can see the front end but not the graphs, like so:

empty graph

I would very appreciate any advice, Thank you

jacekkk avatar Oct 08 '18 11:10 jacekkk

Same issue on Mac as well... connect to port 5000 is refused... not sure whats the issue.. if everything that I need is dockerized than what is it not working...

softwareklinic avatar May 07 '19 17:05 softwareklinic

Did you solve this issue? @softwareklinic @jacekkk ? Having the same one here

rob-bar avatar Jan 28 '20 12:01 rob-bar

You shall use docker compose instead, which will build a network for you.

lucribas avatar Jan 08 '21 14:01 lucribas