Building kolla-ansible in china region
Folks, I am trying to build kolla-ansible in China but somehow my docker repository not accessible. I understand geo location and the great firewall. Does anyone know if there is any local china repo or docker hub which I can use in that region to build the openstack. # docker run -d --network host --name registry --restart=always -e REGISTRY_HTTP_ADDR=0.0.0.0:4000 -v registry:/var/lib/registry registry:2 Unable to find image 'registry:2' locally docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers). See 'docker run --help'.
Hi Satish, To work around Docker Hub rate limits, kolla-ansible CI has recently switched to using libpod from Quay.io instead of the Docker registry image: https://opendev.org/openstack/kolla-ansible/commit/1cec85d680f2528a817e827c0... This could help resolve your error, assuming you don't have the same issues accessing Quay.io. Cheers, Pierre Riteau (priteau) On Thu, 6 Feb 2025 at 15:15, Satish Patel <satish.txt@gmail.com> wrote:
Folks,
I am trying to build kolla-ansible in China but somehow my docker repository not accessible. I understand geo location and the great firewall. Does anyone know if there is any local china repo or docker hub which I can use in that region to build the openstack.
# docker run -d --network host --name registry --restart=always -e REGISTRY_HTTP_ADDR=0.0.0.0:4000 -v registry:/var/lib/registry registry:2 Unable to find image 'registry:2' locally docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers). See 'docker run --help'.
On 2025-02-06 18:09:43 +0100 (+0100), Pierre Riteau wrote:
To work around Docker Hub rate limits, kolla-ansible CI has recently switched to using libpod from Quay.io instead of the Docker registry image: https://opendev.org/openstack/kolla-ansible/commit/1cec85d680f2528a817e827c0... This could help resolve your error, assuming you don't have the same issues accessing Quay.io. [...]
Also worth pointing out that there was a lengthy DockerHub outage in the past day, so might be a good idea to try again just in case that was the problem: https://www.dockerstatus.com/pages/history/533c6539221ae15e3f000031 -- Jeremy Stanley
participants (3)
-
Jeremy Stanley
-
Pierre Riteau
-
Satish Patel