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
- install docker for mac beta according to instructions
- open terminal
- sudo bash (see other comment on this problem)
- 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