Docker Community Forums

Share and learn in the Docker community.

Cannot pull from private repo on VPN


(Charlesporter) #1

Expected behavior

able to pull from internal company repo over VPN (worked with docker-machine and docker-vpn-helper)

Actual behavior

error pulling internal docker repo
See error in repro steps, below

Information

  • running F5 Big_IP edge client

  • and Enterpise Connect

  • With docker-machine was able to get this to work using docker-vpn-helper

  • I am able to pull from docker.io if I disconnect from VPN

  • internal registry is V2.

  • the output of: pinata diagnose -u on OSX
    f45c89ad2fc9:docker xmf453$ pinata diagnose -u
    Error exec: /usr/bin/curl -L -X PUT -T ‘/tmp/20160521-200115.tar.gz’ -H ‘Host: docker-pinata-support’ -H ‘Date: Sat, 21 May 2016 20:01:19 EDT’ -H ‘x-amz-acl: bucket-owner-full-control’ -H ‘Content-type: application/json’ https://docker-pinata-support.s3.amazonaws.com/incoming/2/C187BCEB-6CD6-4320-A92A-228C30D5BB26/20160521-200115/report.tar: exit 5
    diagnose: internal error, uncaught exception:
    Misc.Failure

    • a reproducible case if this is a bug, Dockerfiles FTW
    • host distribution and version
      OSX 10.11.4)

Steps to reproduce the behavior

  1. install docker for mac beta according to instructions
  2. open terminal
  3. sudo bash (see other comment on this problem)
  4. docker pull my-private-docker-registry/my-namespace/my-repo
    Using default tag: latest
    Error response from daemon: Get https://my-private-docker-registry/my-namespace/my-repo/v1/_ping: dial tcp: lookup my-private-docker-registry on :53: server misbehaving

(Alex Sherwin) #2

Seeing the same thing after upgrading to beta 12.

Only way I’ve overcome it is to:

  1. Connect to VPN
  2. Edit my current network interface, manually configure the OS X Network DNS settings to point to the DNS server on my remote VPN network
  3. Restart Docker app

Being that this is the only way I’ve been able to make it work, I presume it’s an issue with how DNS resolution is getting done… I didn’t have this problem before beta 12


(Charlesporter) #3

Thanks for the suggestion.
I look at my DNS settings, seem to be ok.
I guess I will have to wait for the next release