Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was getting a
listing workers: failed to list workers: rpc error: code = DeadlineExceeded desc = context deadline exceeded
error when runningdocker buildx ls
anddocker buildx inspect
with the Kubernetes driver, some of the time:$ docker buildx inspect Name: cool_fermi Driver: kubernetes Nodes: Name: buildx0-6dcb5544c6-457mv Endpoint: Error: listing workers: failed to list workers: rpc error: code = DeadlineExceeded desc = context deadline exceeded $ docker buildx ls NAME/NODE DRIVER/ENDPOINT STATUS PLATFORMS cool_fermi * kubernetes buildx0-6dcb5544c6-457mv listing workers: failed to list workers: rpc error: code = DeadlineExceeded desc = context deadline exceeded default docker default default running linux/amd64, linux/arm64, linux/ppc64le, linux/s390x, linux/386, linux/arm/v7, linux/arm/v6
I was able to resolve this by increasing the context timeout of both commands from 5 and 7 seconds to 20 seconds. This might be because I am on a satellite internet connection with higher latency to the Kubernetes cluster in the cloud.