No running builder detected during build, "ERROR: expected 1 replicas to be ready, got 0"
gitfxx opened this issue · comments
Contributing guidelines
- I've read the contributing guidelines and wholeheartedly agree
I've found a bug and checked that ...
- ... the documentation does not mention anything about my problem
- ... there are no open or closed issues that are related to my problem
Description
I've already started the BuildKit service and the builder's status is running when creating the builder. Why is it necessary to restart the BuildKit service when executing 'buildx build'?
[2024-05-11 15:08:51.643] + wget -q -O /k8s-config-x86 ********/x86-config
[2024-05-11 15:08:51.643] + wget -q -O /k8s-config-arm ********/arm-config
[2024-05-11 15:08:51.643] + KUBECONFIG=/k8s-config-x86 buildx create --use --bootstrap '--name=builder-test' '--driver=kubernetes' '--platform=linux/amd64' '--node=builder-test-amd64' '--driver-opt=namespace=buildx-builder,image=buildkit:0.9.0-c,nodeselector=pipeline=buildx-builder'
[2024-05-11 15:08:51.643] #1 [internal] booting buildkit
[2024-05-11 15:08:51.643] #1 waiting for 1 pods to be ready
[2024-05-11 15:08:52.311] #1 waiting for 1 pods to be ready 1.4s done
[2024-05-11 15:08:52.311] #1 DONE 1.4s
[2024-05-11 15:08:52.311] builder-test
[2024-05-11 15:08:52.311] + KUBECONFIG=/k8s-config-arm buildx create --bootstrap --append '--name=builder-test' '--driver=kubernetes' '--platform=linux/arm64' '--node=builder-test-arm64' '--driver-opt=namespace=buildx-builder,image=buildkit:0.9.0-c-arm64,nodeselector=buildx-builder=arm64'
[2024-05-11 15:08:52.630] #1 [internal] booting buildkit
[2024-05-11 15:08:52.936] #1 waiting for 1 pods to be ready
[2024-05-11 15:08:57.471] #1 waiting for 1 pods to be ready 4.2s done
[2024-05-11 15:08:57.471] #1 DONE 4.4s
[2024-05-11 15:08:57.471] builder-test
[2024-05-11 15:08:57.471] + buildx ls
[2024-05-11 15:08:57.471] NAME/NODE DRIVER/ENDPOINT STATUS PLATFORMS
[2024-05-11 15:08:57.471] builder-test * kubernetes
[2024-05-11 15:08:57.471] builder-test-amd64-69ddd65794-6hz4p running linux/amd64*, linux/386
[2024-05-11 15:08:57.471] builder-test-arm64-68746bb748-lrq6m running linux/arm64*
[2024-05-11 15:08:57.471] default docker-container
[2024-05-11 15:08:57.471] default default Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
[2024-05-11 15:08:57.471] + sss=bbb buildx build '--builder=builder-test' --secret 'id=sss' '--platform=linux/amd64,linux/arm64' -t test:test123213 -f ./Dockerfile .
[2024-05-11 15:08:57.471] time="2024-05-11T07:08:57Z" level=warning msg="No output specified for kubernetes driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load"
[2024-05-11 15:08:57.471] #1 [internal] booting buildkit
[2024-05-11 15:08:57.471] #1 waiting for 1 pods to be ready
[2024-05-11 15:10:50.297] #1 waiting for 1 pods to be ready 109.3s done
[2024-05-11 15:10:50.297] #1 ERROR: expected 1 replicas to be ready, got 0
Expected behaviour
Executing 'buildx build' does not require restarting the BuildKit service.
Actual behaviour
Executing 'buildx build' may sometimes result in restarting and failing to launch pods.
[2024-05-11 15:08:57.471] #1 [internal] booting buildkit
[2024-05-11 15:08:57.471] #1 waiting for 1 pods to be ready
[2024-05-11 15:10:50.297] #1 waiting for 1 pods to be ready 109.3s done
[2024-05-11 15:10:50.297] #1 ERROR: expected 1 replicas to be ready, got 0
Buildx version
v0.7.0
Docker info
none
Builders list
[2024-05-11 15:08:57.471] + buildx ls
[2024-05-11 15:08:57.471] NAME/NODE DRIVER/ENDPOINT STATUS PLATFORMS
[2024-05-11 15:08:57.471] builder-test * kubernetes
[2024-05-11 15:08:57.471] builder-test-amd64-69ddd65794-6hz4p running linux/amd64*, linux/386
[2024-05-11 15:08:57.471] builder-test-arm64-68746bb748-lrq6m running linux/arm64*
[2024-05-11 15:08:57.471] default docker-container
[2024-05-11 15:08:57.471] default default Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Configuration
none
Build logs
[2024-05-11 15:08:51.643] + wget -q -O /k8s-config-x86 ********/cke-config
[2024-05-11 15:08:51.643] + wget -q -O /k8s-config-arm ********/k8s-config
[2024-05-11 15:08:51.643] + KUBECONFIG=/k8s-config-x86 buildx create --use --bootstrap '--name=builder-test' '--driver=kubernetes' '--platform=linux/amd64' '--node=builder-test-amd64' '--driver-opt=namespace=buildx-builder,image=buildkit:0.9.0-c,nodeselector=pipeline=buildx-builder'
[2024-05-11 15:08:51.643] #1 [internal] booting buildkit
[2024-05-11 15:08:51.643] #1 waiting for 1 pods to be ready
[2024-05-11 15:08:52.311] #1 waiting for 1 pods to be ready 1.4s done
[2024-05-11 15:08:52.311] #1 DONE 1.4s
[2024-05-11 15:08:52.311] builder-test
[2024-05-11 15:08:52.311] + KUBECONFIG=/k8s-config-arm buildx create --bootstrap --append '--name=builder-test' '--driver=kubernetes' '--platform=linux/arm64' '--node=builder-test-arm64' '--driver-opt=namespace=buildx-builder,image=buildkit:0.9.0-c-arm64,nodeselector=buildx-builder=arm64'
[2024-05-11 15:08:52.630] #1 [internal] booting buildkit
[2024-05-11 15:08:52.936] #1 waiting for 1 pods to be ready
[2024-05-11 15:08:57.471] #1 waiting for 1 pods to be ready 4.2s done
[2024-05-11 15:08:57.471] #1 DONE 4.4s
[2024-05-11 15:08:57.471] builder-test
[2024-05-11 15:08:57.471] + buildx ls
[2024-05-11 15:08:57.471] NAME/NODE DRIVER/ENDPOINT STATUS PLATFORMS
[2024-05-11 15:08:57.471] builder-test * kubernetes
[2024-05-11 15:08:57.471] builder-test-amd64-69ddd65794-6hz4p running linux/amd64*, linux/386
[2024-05-11 15:08:57.471] builder-test-arm64-68746bb748-lrq6m running linux/arm64*
[2024-05-11 15:08:57.471] default docker-container
[2024-05-11 15:08:57.471] default default Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
[2024-05-11 15:08:57.471] + sss=bbb buildx build '--builder=builder-test' --secret 'id=sss' '--platform=linux/amd64,linux/arm64' -t test:test123213 -f ./Dockerfile .
[2024-05-11 15:08:57.471] time="2024-05-11T07:08:57Z" level=warning msg="No output specified for kubernetes driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load"
[2024-05-11 15:08:57.471] #1 [internal] booting buildkit
[2024-05-11 15:08:57.471] #1 waiting for 1 pods to be ready
[2024-05-11 15:10:50.297] #1 waiting for 1 pods to be ready 109.3s done
[2024-05-11 15:10:50.297] #1 ERROR: expected 1 replicas to be ready, got 0
### Additional info
_No response_