Docker Community Forums

Share and learn in the Docker community.

Docker Beta on macOS Sierra 10.12


(Doc1) #1

Expected behavior

‘docker pull imagename’ will pull down a docker image

Actual behavior

Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/redis/images. You may want to check your internet connection or if you are behind a proxy.

Information

Docker for Mac: version: mac-v1.11.2-beta15
OS X: version 10.12 (build: 16A201w)
logs: /tmp/20160616-165842.tar.gz
failure: No error was detected
[OK] docker-cli
[OK] app
[OK] menubar
[OK] virtualization
[OK] system
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce the behavior

  1. Install macOS Sierra beta
  2. Install Docker for Mac beta
  3. Docker pull imagename

(Ckopper) #2

I was just about to submit the exact same post - I can confirm that Docker for Mac fails in this way on my macOS 10.12 system (it is able to access the network on 10.11 as expected, of course). I guess these things are fully expected when running on a developer preview version, but maybe this feedback is useful to the developers.


(Doc1) #3

@ckopper I’ve changed networks and docker is not working as expected. Was just going to update this post that the issue was my (assuming network related) but now seeing someone else with the same issue it adds some credibility to the issue. Have you noticed a difference in this behaviour from network to network. In my case I noticed this at the office and now seems to be working again on the hotel network.


(Ckopper) #4

Interesting! Since you mentioned it might be network-related, I tried it tethered to my phone and it worked. One of the differences seems to be that my office and home networks have IPv6 but my phone tethering is IPv4-only. I checked and I could also make it work on my original network by disabling IPv6 (or, rather, setting it to “link-local only”), so this might have something to do with it?

I guess you could try if you can make it work at your office network by trying to turn off IPv6 to see if it is the same issue. If that’s the case, this might be easy to fix for the Docker for Mac developers.


(Donald Piret) #5

Had this issue as well and can confirm that disabling IPv6 solves the issue for me. Just go to the network settings -> Advanced -> TCP/IP and configure IPv6 to link-local only.


(David Wisner) #6

I forgot to reply here but disabling IPv6 - either by switching to link local (works of my router) or using the cmdline to turn off ipv6 or just turning it off in your router fixed then problem. Overall docker seems compatible with 10.12 - however I’ve have to completely uninstall / reinstall docked 2/3 times - so it’s stability is not consistent between startups, but I haven’t noticed docker crashing while running. I was able compile the firmware for one of my routers, which is a process that takes 2-4 hours, and had previously failed in the past (last attempt was 4-5 beta releases ago) - but using that as my metric, I was pleasantly surprised that docker worked, period


(Matt Robenolt) #7

I can confirm this as well, and here are the logs from Console:

Jul 10 20:39:13 Matts-iMac Docker[4649]: Using protocol TwoThousand msize 8192
Jul 10 20:39:15 Matts-iMac Docker[4651]: Docker is responding
Jul 10 20:39:15 Matts-iMac Docker[4650]: Failed to read the last-shutdown-time key: strconv.ParseInt: parsing "": invalid syntax
Jul 10 20:39:15 Matts-iMac Docker[4650]: VM started at 2016-07-10 20:39:15 -0700 PDT
Jul 10 20:39:15 Matts-iMac Docker[4629]: dockerState = Starting
Jul 10 20:39:45 Matts-iMac Docker[4649]: Socket.TCPV4.read 54.192.117.184:443: caught Uwt.Uwt_error(Uwt.ECONNRESET, "uwt_read", "") returning Eof

(Joshua Wiens) #8

Same issue - docker pull node

ul 14 12:07:57 Joshuas-MacBook-Pro-2 Docker[494]: VM: 2016-07-14 17:07:57 +0000 UTC daemon.info vsudd: Connection 5 to: 2376 from: 00000000 Jul 14 12:07:57 Joshuas-MacBook-Pro-2 Docker[494]: VM: 2016-07-14 17:07:57 +0000 UTC daemon.info vsudd: 5 Done. read: 89 written: 1787 Jul 14 12:07:57 Joshuas-MacBook-Pro-2 Docker[494]: VM: 2016-07-14 17:07:57 +0000 UTC daemon.info vsudd: Connection 6 to: 2376 from: 00000000 Jul 14 12:07:58 Joshuas-MacBook-Pro-2 Docker[494]: VM: 2016-07-14 17:07:58 +0000 UTC daemon.info vsudd: 6 Done. read: 313 written: 380 Jul 14 12:07:59 Joshuas-MacBook-Pro-2 com.apple.xpc.launchd[1] (com.apple.locationmenu): Service only ran for 0 seconds. Pushing respawn out by 10 seconds. Jul 14 12:08:20 Joshuas-MacBook-Pro-2 Docker[494]: VM: 2016-07-14 17:08:20 +0000 UTC daemon.info vsudd: Connection 7 to: 2376 from: 00000000 Jul 14 12:08:20 Joshuas-MacBook-Pro-2 Docker[494]: VM: 2016-07-14 17:08:20 +0000 UTC daemon.info vsudd: 7 Done. read: 89 written: 1787 Jul 14 12:08:20 Joshuas-MacBook-Pro-2 Docker[494]: VM: 2016-07-14 17:08:20 +0000 UTC daemon.info vsudd: Connection 8 to: 2376 from: 00000000 Jul 14 12:08:22 Joshuas-MacBook-Pro-2 Docker[492]: Socket.TCPV4.read 52.84.0.58:443: caught Uwt.Uwt_error(Uwt.ECONNRESET, "uwt_read", "") returning Eof


(Benmarte) #9

I can confirm this fixed it for me, thanks for sharing the info.


(David Wisner) #10

doesnt work anymore…


(Doc1) #11

I’m seeing same - even with IPV6 set to link local this is broken now. Does anyone from Docker patrol these forums? Is there an issue logged for this?


(David Wisner) #12

Oh the solution exist… somewhere on this forum…

sudo launchctl unload /System/Library/LaunchDaemons/org.ntp.ntpd.plist

not sure why the ntp daemon is responsible - probably something inside the vm not being able to sync with the local time


(Doc1) #13

This doesn’t seem to work for me … unloaded the plist but same issue. :frowning:


(Leonidas Tsementzis) #14

Stopping the NTP daemon fixed it for me.
Perhaps the underlying problem is related to this macOS Sierra change https://github.com/golang/go/commit/53da5fd?