Closed erip closed 6 years ago
Ah... upon creation of the cluster, NO_PROXY
will need to be re-exported... $ export NO_PROXY="$no_proxy,$(minikube ip)"
made ~this work~ it get further.
Despite this, I'm still seeing the following my my logs:
Error response from daemon: Get https://gcr.io/v2/: x509: certificate signed by unknown authority
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
I'm also facing the same issue while running behind corporate proxy. Is there any way to accept the certificate to allow downloading the images?
Environment:
What happened:
What you expected to happen:
A successful creation of a deployment.
How to reproduce it (as minimally and precisely as possible):
Difficult since it's environment-specific...
Output of
minikube logs
(if applicable):