Docker Community Forums

Share and learn in the Docker community.

1.11.1-beta12 - problem pushing to private registry


(Tmiklas) #1

Expected behavior

On ‘docker push’ to a properly deployed registry, the push should finish in one go, no stalled uploads, no retries, no aborted and broken uploads. Linux docker client does exactly that - every time, 1.11.1-beta12 on Mac fails. In both cases I push the same images against the same registry - one works, one doesn’t.

I didn’t notice this behavior in previous beta release - i.e. before last update. Is it just me experiencing this?

Actual behavior

Tiny layers make it to the registry OK,
Anything bigger than few MB get stuck every 1-1.5MB, goes to retry, fails after a couple retries.
Screenshot 1:
Screenshot 2:


Tomaszs-MacBook-Pro:~ tm$ pinata diagnose -u
OS X: version 10.11.4 (build: 15E65) version v1.11.1-beta12
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/20160519-205146.tar.gz
Most specific failure is: No error was detected
Your unique id is: A653F7ED-7D10-46E0-9831-B6B90ACB84E0
Please quote this in all correspondence.

Steps to reproduce the behavior

  1. Deploy registry v2 following standard deployment steps (see docs) - ca be secure or insecure, with/without authentication - no difference
  2. Tag any local image
  3. Push tagged image to private registry