Unable to connect to the server: certificate is not valid for host.docker.internal

[Aisuko]

• VSCode Version:

Version: 1.47.3
Commit: 91899dcef7b8110878ea59626991a18c8a6a1b3e
Date: 2020-07-23T13:08:29.692Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.6.0

• Local OS Version:
  macOS Catalina
• Name of Dev Container Definition with Issue: Kubernetes & Helm

Steps to Reproduce:

1. mount the /.kube and /.minikube folder into the container and run the command with kubectl

root@0ab3a3828ae9:/workspaces/meshery-linkerd# kubectl cluster-info

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
Unable to connect to the server: x509: certificate is valid for minikubeCA, control-plane.minikube.internal, kubernetes.default.svc.cluster.local, kubernetes.default.svc, kubernetes.default, kubernetes, localhost, not host.docker.internal

root@0ab3a3828ae9:/workspaces/meshery-linkerd# kubectl cluster-info --insecure-skip-tls-verify
Kubernetes master is running at https://host.docker.internal:32772
KubeDNS is running at https://host.docker.internal:32772/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
root@0ab3a3828ae9:/workspaces/meshery-linkerd# kubectl config view
apiVersion: v1
clusters:
- cluster:
    certificate-authority: /root/.minikube/ca.crt
    server: https://host.docker.internal:32772
  name: minikube
contexts:
- context:
    cluster: minikube
    user: minikube
  name: minikube
current-context: minikube
kind: Config
preferences: {}
users:
- name: minikube
  user:
    client-certificate: /root/.minikube/client.crt
    client-key: /root/.minikube/client.key

The same issue I hit on kubernetes/Kind(macOS local executing kind create cluster and try to communicate the cluster in the (1kubernetes&helm1 which same host different container) and kind get kubeconfig --name kind --internal useless for me)

[Chuxel]

I use minikube on Linux, but I use Docker's built in Kubernetes on Mac and both appear to work as expected. What is your cert/key tied to? If it's 127.0.0.1 or localhost, that won't work unfortunatley.

[Aisuko]

I use minikube start and kind create cluster command on macOS and Ubuntu20.04

The server filed in the kubeconfig

Result	kind@v0.8.1	minikube@v1.12.1(mac)/v1.11.1(ubuntu20.04)
Ubuntu20.04	server: https://127.0.0.1:35309	server: https://172.17.0.3:8443
macOS Catalina	server: https://127.0.0.1:61531	server: https://127.0.0.1:32772

I do not use Docker-for-mac's Kubernetes feature.

Oh, I see:

• On macOS use Docker's built-in Kubernetes feature(I don't like the built-in Kubernetes🧐)
• Or change the docker context on macOS to the Linux which running minikube.

[Chuxel]

Yeah the problem is that 127.0.0.1 will resolve to the container itself. Using host networking and removing the translation to host.docker.internal might work (have not tried). You could also ensure your cert allows host.docker.internal.

[Chuxel]

Added a note on this to the README since I can see how this would be confusing: https://github.com/microsoft/vscode-dev-containers/tree/master/containers/kubernetes-helm#a-note-on-minkube-or-otherwise-using-a-local-cluster

[Aisuko]

Yeah the problem is that 127.0.0.1 will resolve to the container itself. Using host networking and removing the translation to host.docker.internal might work (have not tried). You could also ensure your cert allows host.docker.internal.

Yep, that would be one of the solutions, I believe we can close this issue.