Docker Community Forums

Share and learn in the Docker community.

OSX connection sharing confuses Docker for Mac


(Mangled Deutz) #1

Expected behavior

Network works.

Actual behavior

Network does not work :slight_smile:

Information

OSX 10.11.4

dmp@MacMorteau:~$ pinata diagnose -u OS X: version 10.11.4 (build: 15E65) Docker.app: version v1.11.0-beta6 Running diagnostic tests: [ERROR] docker-cli wrong Docker version: 1.10.2 (expected 1.11.0-rc3) [OK] Moby booted [OK] driver.amd64-linux [OK] vmnetd [OK] osxfs [OK] db [OK] slirp [OK] menubar [OK] environment [OK] Docker [OK] VT-x Docker logs are being collected into /tmp/20160408-182754.tar.gz. Your unique id in bugsnag is: 0D5131EF-39CE-4CAB-B494-C20660FC938B Please quote this in all correspondence.

Steps to reproduce the behavior

  1. Start docker
  2. Enable OSX connection sharing from eth-usb to wifi
  3. docker pull golang
  4. Result: Network timed out while trying to connect to https://index.docker.io/v1/repositories/armhf/debian/images. You may want to check your internet connection or if you are behind a proxy.
  5. unplug the usb-eth adapter to bring the eth interface down
  6. docker pull golang
  7. Error while pulling image: Get https://index.docker.io/v1/repositories/armhf/debian/images: dial tcp: lookup index.docker.io on 192.168.64.1:53: read udp 192.168.64.2:36478->192.168.64.1:53: read: connection refused

At this point, docker is in a non-functional state (have to restart Docker).


(Birgerk) #2

some problem, but got not that docker-cli-version problem:

OS X: version 10.11.5 (build: 15F34)
Docker.app: version v1.11.1-beta13.1
Running diagnostic tests:
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160602-142117.tar.gz
Most specific failure is: No error was detected
Your unique id is: F231726C-4F88-400C-A4C2-D70C210A4DC6
Please quote this in all correspondence.

and I got a newer version. Anyone an idea about this?
Only workaround is a restart of the app. and that sucks :frowning: