Closed cvila84 closed 8 months ago
@afbjorklund hello ! do you need other information to consider it as an issue ? thanks !
For clarity, HTTP proxies are working well with docker as container runtime but are not with containerd (this issue).
IMO, this could become a wider problem as almost everybody will move to containerd sooner or later (because of deprecation).
@afbjorklund what do you think ?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
What Happened?
During our tests to replace docker by containerd as container runtime, we can't start a minikube VM behind a HTTP proxy. It seems the settings are not propagated in this case :
https://github.com/kubernetes/minikube/blob/3f893a2feeb5f61514b28a708892b136000dcc22/pkg/provision/provision.go#L230-L238
K8S images cannot be pulled during kubeadm as the direct connection times out
Attach the log file
Operating System
Windows
Driver
VirtualBox