Welcome to the Linux Foundation Forum!

Exercise 3.2: Configure A Local Docker Repo - Unable to Push to Local Docker Repo

Hi all,
My Kubernetes cluster is setup behind a proxy, and I have had to create NO_PROXY entries for cluster nodes and services in the /etc/systemd/system/docker.service.d/http-proxy.conf file.

where "" is the service/registry ClusterIP

All looks good with the Local docker repo setup on this Exercise 3.2, till the point of pushing the docker image to the local repo.
It fails with error : Client.Timeout exceeded while awaiting headers

[email protected]:~# sudo docker push
The push refers to repository []
Get net/http: request canceled (Client.Timeout exceeded while awaiting headers)

The registry and nginx pods are running, as below;
[email protected]:~# kubectl get pod
nginx-f875c68bb-mtxhv 1/1 Running 0 3h20m
registry-7ccd695dc7-4d8px 1/1 Running 0 3h20m

  • curl

    {}[email protected]

  • sudo vim /etc/docker/daemon.json
    { "insecure-registries":[""] }

  • sudo systemctl status docker.service | grep Active

    Active: active (running) since Sun 2020-05-10 13:27:36 UTC; 15min ago

Anybody experienced similar issue with pushing docker images to a local repo? Can anyone please with this?


  • chrispokornichrispokorni Posts: 509

    Hi @eromskiee,

    While the NO_PROXY seems to be a common fix when running behind a proxy, there may be other settings specific to your own environment that should also be examined. Your hypervisor, cloud provider, operating system, and possibly others play a key role in figuring out what causes the timeout. I would start by looking at firewalls, both at your infra level and OS level as most often they are the reason users experience timeouts.


Sign In or Register to comment.