Kind: Containerd is not working behind a proxy

Created on 5 Jul 2019  路  2Comments  路  Source: kubernetes-sigs/kind

What happened:

Containerd is not able to pull images if is working behind a proxy

What you expected to happen:

containerd should work behind a proxy

How to reproduce it (as minimally and precisely as possible):

https://kubernetes.slack.com/archives/CEKK1KTN2/p1562335808184900

Anything else we need to know?:

The problem is that we removed /etc/systemd/system/containerd.service.d/http-proxy.conf

when we merged this https://github.com/kubernetes-sigs/kind/pull/628

Environment:

  • kind version: (use kind version): > 0.4.0
  • Kubernetes version: (use kubectl version):
  • Docker version: (use docker info):
  • OS (e.g. from /etc/os-release):
kinbug prioritimportant-soon

Most helpful comment

as a workaround you can execute in each node

cat <<EOF >/etc/systemd/system/containerd.service.d/http-proxy.conf    
[Service]    
Environment="HTTP_PROXY=${HTTP_PROXY:-}"    
Environment="HTTPS_PROXY=${HTTPS_PROXY:-}"    
Environment="NO_PROXY=${NO_PROXY:-localhost},${LOCAL_NETWORK}"    
EOF

reload the systemd configuration: systemctl daemon-reload

and restart containerd: systemctl restart containerd

@BenTheElder should we recover the images/base/entrypoint ?

All 2 comments

as a workaround you can execute in each node

cat <<EOF >/etc/systemd/system/containerd.service.d/http-proxy.conf    
[Service]    
Environment="HTTP_PROXY=${HTTP_PROXY:-}"    
Environment="HTTPS_PROXY=${HTTPS_PROXY:-}"    
Environment="NO_PROXY=${NO_PROXY:-localhost},${LOCAL_NETWORK}"    
EOF

reload the systemd configuration: systemctl daemon-reload

and restart containerd: systemctl restart containerd

@BenTheElder should we recover the images/base/entrypoint ?

Fixed by #694

Was this page helpful?
0 / 5 - 0 ratings