Skip to content

[SPARK-59212][K8S][INFRA] Pin the Minikube container runtime to docker in K8s CI - #58533

Open
szehon-ho wants to merge 1 commit into
apache:branch-4.3from
szehon-ho:codex/SPARK-59212-minikube-docker-runtime-4.3
Open

[SPARK-59212][K8S][INFRA] Pin the Minikube container runtime to docker in K8s CI#58533
szehon-ho wants to merge 1 commit into
apache:branch-4.3from
szehon-ho:codex/SPARK-59212-minikube-docker-runtime-4.3

Conversation

@szehon-ho

Copy link
Copy Markdown
Member

What changes were proposed in this pull request?

Backport the applicable part of #58502 (680855bea73) to branch-4.3 by passing container-runtime: docker to the Minikube setup used by the Kubernetes integration test job.

The OIDC E2E job updated by the master change does not exist on branch-4.3, so this backport changes only the Kubernetes integration test job.

Why are the changes needed?

Minikube 1.39.0 changed its default container runtime from Docker to containerd. The Kubernetes integration test builds Spark images through minikube docker-env, but the containerd Docker shim does not implement enough of the Docker API for Buildx. Image construction therefore fails while booting BuildKit with:

failed to inspect pulled image moby/buildkit:buildx-stable-1: Error response from daemon: 404 page not found

This currently breaks the branch-4.3 Kubernetes integration check, as seen in this CI run. Pinning the runtime to Docker restores the real Docker daemon expected by the image build.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

  • Parsed .github/workflows/build_and_test.yml with Ruby YAML to verify its syntax.
  • Ran git diff --check.
  • The Kubernetes integration CI job exercises the affected image-build path.

Was this patch authored or co-authored using generative AI tooling?

Generated-by: Codex (GPT-5)

@szehon-ho

Copy link
Copy Markdown
Member Author

hit this build failure on 4.3 as well.. fyi @RamonZhou @dongjoon-hyun

@dongjoon-hyun

Copy link
Copy Markdown
Member

cc @HeartSaVioR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants