Open LeviticusMB opened 4 years ago
Maybe you need to set KUBECONFIG explicitly
OK tried that (export KUBECONFIG=~/.kube/config
) but i get the same error. Any flag I can use to activate some kind of debug logs?
Hi,
I have the issue with rancher 2.4.5.
Hi, I'm also currious why it's not working. I'm also testing Buildx against a Rancher 2.4.5 Cluster with Kubernetes 1.17.6. I've deployed buildkitd as a statefulset by hand, is there a way to add the builder manually?
I did some digging and it appears that Rancher uses a bearer token for authentication. The kubernetes builder driver loads the kubeconfig using the docker cli context api, which unfortunately ignores the token in the kubeconfig (see https://github.com/docker/cli/issues/1852).
I have not found a workaround yet
Trying to test the
kubernetes
driver. Created the builder usingbut when I try to build something, it fails with:
Not sure what to try next? I can create new pods just find on the command line:
Background info:
The server is a Rancher v2.3.5 Kubernetes cluster.