'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.

  • BitBucket pipelines - docker unauthorized: authentication required - Docker push with successful login
  • How do I use Docker on BitBucket pipelines to test a Django app that needs PostGIS?
  • Bitbucket Pipeline how to setup ssh agent to deploy on a remote server
  • trouble with running e2e on bitbucket pipeline
  • What docker image use for ionic CD / e2e testing? Ubuntu or just node?
  • Is there an easy way to change to a non-root user in Bitbucket Pipelines Docker container?
  • docker-machine create error … VBoxManage: error: Unknown option: --synthcpu
  • Apache Drill in Docker container: java.net.BindException: Address already in use
  • How can I make all my docker containers use my proxy?
  • Docker container detected! Ruxit Agent cannot be installed
  • How to push an image id to docker repo
  • Encrypted and secure docker containers
  • 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.