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

push to local registry failed with error: getsockopt: no route to host #1797

Closed
Diluka opened this issue Jun 30, 2017 · 6 comments

Comments

@Diluka
Copy link

commented Jun 30, 2017

Expected behavior

push successful

Actual behavior

push failed

Information

  • Full output of the diagnostics from "Diagnose & Feedback" in the menu
Docker for Mac: version: 17.06.0-ce-mac18 (4cdec4294a50b2233146b09469b49937dabdebdd)
macOS: version 10.12.5 (build: 16F73)
logs: /tmp/DD18080C-77CE-4235-A276-14C957B3F8F4/20170630-163037.tar.gz
[OK]     db.git
[OK]     vmnetd
[OK]     dns
[OK]     driver.amd64-linux
[OK]     virtualization VT-X
[OK]     app
[OK]     moby
[OK]     system
[OK]     moby-syslog
[OK]     db
[OK]     env
[OK]     virtualization kern.hv_support
[OK]     slirp
[OK]     osxfs
[OK]     moby-console
[OK]     logs
[OK]     docker-cli
[OK]     menubar
[OK]     disk
  • A reproducible case if this is a bug, Dockerfiles FTW
  • Page URL if this is a docs issue or the name of a man page

Steps to reproduce the behavior

  1. pull an image
$ docker pull hello-world
Using default tag: latest
latest: Pulling from library/hello-world
b04784fba78d: Pull complete 
Digest: sha256:f3b3b28a45160805bb16542c9531888519430e9e6d6ffc09d72261b0d26ff74f
Status: Downloaded newer image for hello-world:latest
  1. tag a name
$ docker tag hello-world 192.168.65.80:5000/test/hello
  1. push to registry
$ docker push 192.168.65.80:5000/test/hello
The push refers to a repository [192.168.65.80:5000/test/hello]
Get http://192.168.65.80:5000/v2/: dial tcp 192.168.65.80:5000: getsockopt: no route to host
  1. I do exactly the same on ubuntu and succeeded!
The push refers to a repository [192.168.65.80:5000/test/hello]
45761469c965: Pushed 
latest: digest: sha256:9fa82f24cbb11b6b80d5c88e0e10c3306707d97ff862a3018f22f9b49cef303a size: 524

mac, ubuntu and registry there have different IPs, but in the same local network.

@djs55

This comment has been minimized.

Copy link
Contributor

commented Jul 14, 2017

Thanks for your report.

I believe this is the same as #1803: there is a clash between the internal network used by Docker for Mac and a network in your environment. In the short term, here are some instructions describing how to customise the network used by Docker for Mac. The upcoming 17.07 edge release should have a UI element in the preferences which makes this easier.

@Diluka

This comment has been minimized.

Copy link
Author

commented Oct 12, 2017

still failed

Docker for Mac: version: 17.09.0-ce-mac35 (69202b202f497d4b6e627c3370781b9e4b51ec78)
macOS: version 10.13 (build: 17A405)
logs: /tmp/F7F6CDCA-01F1-4E9E-A84A-0F804EC19308/20171012-154615.tar.gz
[OK]     db.git
[OK]     vmnetd
[OK]     dns
[OK]     driver.amd64-linux
[OK]     virtualization VT-X
[OK]     app
[OK]     moby
[OK]     system
[OK]     moby-syslog
[OK]     db
[OK]     env
[OK]     virtualization kern.hv_support
[OK]     slirp
[OK]     osxfs
[OK]     moby-console
[OK]     logs
[OK]     docker-cli
[OK]     menubar
[OK]     disk
@nado18

This comment has been minimized.

Copy link

commented Oct 20, 2017

I had the same issue with 17.09.0-ce-mac35, I installed docker-edge instead (17.09.0ce-mac34) and now I can get back to work, i.e.:

brew tap caskroom/versions
brew cask install docker-edge
@tboyce

This comment has been minimized.

Copy link

commented Nov 5, 2017

Same issue. Had no network conflict here. Just switching to edge also worked for me.

@djs55

This comment has been minimized.

Copy link
Contributor

commented Nov 6, 2017

@Diluka thanks for the report. I had a look and unfortunately discovered a bug in the implementation and a missing test case for the "Docker IP" feature. I've fixed the bug and implemented the test case, so hopefully the Preferences menu -> Advanced -> Docker IP settings should be working in the next edge release. Sorry for the confusion!

@docker-desktop-robot

This comment has been minimized.

Copy link
Collaborator

commented Mar 28, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.