Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

extremely slow pushes to local registry #2339

Closed
caarlos0 opened this issue Dec 17, 2017 · 5 comments
Closed

extremely slow pushes to local registry #2339

caarlos0 opened this issue Dec 17, 2017 · 5 comments

Comments

@caarlos0
Copy link

Expected behavior

I'm running the registry as indicated in the documentation:

$ docker run -d -p 5000:5000 --restart always --name registry registry:2
Unable to find image 'registry:2' locally
2: Pulling from library/registry
ab7e51e37a18: Pull complete
c8ad8919ce25: Pull complete
5808405bc62f: Pull complete
f6000d7b276c: Pull complete
f792fdcd8ff6: Pull complete
Digest: sha256:9d295999d330eba2552f9c78c9f59828af5c9a9c15a3fbd1351df03eaad04c6a
Status: Downloaded newer image for registry:2
72a223c2c6710ef9ab014b2595d5c20a3867bb5577b79fa4a321bdbb637d461d

Pushing an image to the local registry should be fast.

Actual behavior

Pushing images, even very small images (like an scratch + text file or whatever), few Kb only, takes ages.

I tried to docker pull + docker tag + docker push the goreleaser/goreleaser image, which is ~8mb:

$ docker images -a
REPOSITORY                             TAG                 IMAGE ID            CREATED             SIZE
goreleaser/goreleaser                  latest              e4c02016aa2e        24 hours ago        8.03MB
localhost:5000/goreleaser/goreleaser   latest              e4c02016aa2e        24 hours ago        8.03MB
registry                               2                   177391bcf802        2 weeks ago         33.3MB

It took 4m11s to push the 8mb image:

$ docker push localhost:5000/goreleaser/goreleaser
The push refers to a repository [localhost:5000/goreleaser/goreleaser]
3e9ca8759232: Pushed
latest: digest: sha256:1848acb4c37bea4f38ffdf0f98b06f1b1e173d99aa21425874555dfff2067919 size: 528

Pulling the same image after took 1m:

$ docker pull localhost:5000/goreleaser/goreleaser
Using default tag: latest
latest: Pulling from goreleaser/goreleaser
Digest: sha256:1848acb4c37bea4f38ffdf0f98b06f1b1e173d99aa21425874555dfff2067919
Status: Image is up to date for localhost:5000/goreleaser/goreleaser:latest

Information

  • Full output of the diagnostics from "Diagnose & Feedback" in the menu
Docker for Mac: version: 17.09.1-ce-mac42 (69202b202f497d4b6e627c3370781b9e4b51ec78)
macOS: version 10.13.2 (build: 17C88)
logs: /tmp/80AC17A8-A956-4043-829D-86C222427FCA/20171217-205554.tar.gz
[OK]     db.git
[OK]     vmnetd
[OK]     dns
[OK]     driver.amd64-linux
[OK]     virtualization VT-X
[OK]     app
[OK]     moby
[OK]     system
[OK]     moby-syslog
[OK]     db
[OK]     env
[OK]     virtualization kern.hv_support
[OK]     slirp
[OK]     osxfs
[OK]     moby-console
[OK]     logs
[OK]     docker-cli
[OK]     menubar
[OK]     disk
  • A reproducible case if this is a bug, Dockerfiles FTW
$ docker run -d -p 5000:5000 --restart always --name registry registry:2
$ docker pull ubuntu
$ docker tag ubuntu localhost:5000/ubuntu
$ docker push localhost:5000/ubuntu
  • Page URL if this is a docs issue or the name of a man page

Steps to reproduce the behavior

On a mac:

$ docker run -d -p 5000:5000 --restart always --name registry registry:2
$ docker pull ubuntu # could be any img actually
$ docker tag ubuntu localhost:5000/ubuntu
$ docker push localhost:5000/ubuntu
caarlos0 added a commit to goreleaser/goreleaser that referenced this issue Dec 17, 2017
@docker-robott
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

@caarlos0
Copy link
Author

/remove-lifecycle stale

@docker-robott
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

@foobarbecue
Copy link

/remove-lifecycle stale

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jun 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants