You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ docker buildx build --load /Users/mb/source/Till -f /Users/mb/source/Till/docker//till-erp/Dockerfile --build-arg version=dev -t localhost:5000/till-erp:dev
[+] Building 0.0s (1/1) FINISHED
=> ERROR [internal] booting buildkit 0.0s
------
> [internal] booting buildkit:
------
error while calling deploymentClient.Create for "k8s-office0": the server has asked for the client to provide credentials (post deployments.apps)
Not sure what to try next? I can create new pods just find on the command line:
$ kubectl run --image nginx test
kubectl run --generator=deployment/apps.v1 is DEPRECATED and will be removed in a future version. Use kubectl run --generator=run-pod/v1 or kubectl create instead.
deployment.apps/test created
$ kubectl get all
NAME READY STATUS RESTARTS AGE
pod/test-679b667858-5fnnt 1/1 Running 0 13s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.43.0.1 <none> 443/TCP 1y
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
deployment.apps/test 1 1 1 1 13s
NAME DESIRED CURRENT READY AGE
replicaset.apps/test-679b667858 1 1 1 13s
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 docker/cli#1852).
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.
The text was updated successfully, but these errors were encountered: