'docker push …' from Bitbucket Pipelines is very slow to my self-hosted docker registry

I am using Bitbucket Pipelines to build my docker image, and push to my self-hosted docker registry, which is located in China.

Is there any way I can speed up docker push from Bitbucket Pipelines. Otherwise, this features is almost useless.

  • What docker image use for ionic CD / e2e testing? Ubuntu or just node?
  • DOCKER for setting up BitBucket
  • Docker memory limit in pipelines
  • Dockerhub automated build: BitBucket repository with private submodules
  • Trouble executing lsb-release in a Bitbucket Pipelines docker instance
  • Bitbucket Pipeline how to setup ssh agent to deploy on a remote server
  • What does BandwidthIn and BandwidthOut graph represent for a service?
  • Should I add the reverse proxy in the same container as the application on docker?
  • How to ADD all files/directories except a hidden directory like .git in Dockerfile
  • How to pull from private docker repository on docker hub?
  • Container exits if invoked from compose
  • Scaling: Docker containers vs Vms
  • One Solution collect form web for “'docker push …' from Bitbucket Pipelines is very slow to my self-hosted docker registry”

    it seems doubtful that much can be done to alleviate slow pushes given 1) bitbucket pipeline and 2) china registry constraints. you have at least three options if you could lift these constraints:

    1. throw out bitbucket pipelines in favor of self-hosted source control management (gitlab/bitbucket server) and a self-hosted CI system that does pipelines as code (there are many to choose from these days, including jenkins)
    2. throw out your self-hosted registry and use docker hub
    3. self-host your registry in the US (bitbucket cloud and pipelines is probably US East?)
    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.