Open vanppo opened 2 years ago
It seems that k3s does not respect the proxy settings, but nerdctl does
Are you behind a proxy?
It seems that k3s does not respect the proxy settings, but nerdctl does
Are you behind a proxy?
Yep, I am behind a proxy running on my host.
$ cat /etc/rancher/k3s/k3s.env
HTTPS_PROXY='http://192.168.5.2:7890'
HTTP_PROXY='http://192.168.5.2:7890'
http_proxy='http://192.168.5.2:7890'
https_proxy='http://192.168.5.2:7890'
$ env | grep -i proxy
HTTPS_PROXY=http://192.168.5.2:7890
https_proxy=http://192.168.5.2:7890
http_proxy=http://192.168.5.2:7890
HTTP_PROXY=http://192.168.5.2:7890
Description
Unable to create pods after starting due to:
but I can pull image by nerdctl:
Version
colima version: colima version 0.4.4 git commit: 8bb1101a861a8b6d2ef6e16aca97a835f65c4f8f
runtime: containerd arch: aarch64 client: v0.20.0 server: v1.5.8
kubernetes Client Version: v1.24.3 Kustomize Version: v4.5.4 Server Version: v1.23.6+k3s1
limactl version: 0.11.2
qemu-img version: 7.0.0
Operating System
Reproduction Steps
Expected behaviour
It seems that k3s does not respect the proxy settings, but nerdctl does.
Additional context
No response