could not bootstrap kubernetes cluster with CNI flannel

[STRRL]

What Happened?

minikube version

minikube version
minikube version: v1.26.1
commit: 62e108c3dfdec8029a890ad6d8ef96b6461426dc

step to reproduce:

• execute minikube start --cni flannel
• every workload (including coredns) would stuck in ContainerCreating
• execute k describe pod -n kube-system coredns-x-x

There would be some error message in the event

  Warning  FailedCreatePodSandBox  3m                kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = [failed to set up sandbox container "b17871cf37fec75d431480096c668f785d555f2b07d94ce1e699a9590d4f54e0" network for pod "coredns-6d4b75cb6d-78ktc": networkPlugin cni failed to set up pod "coredns-6d4b75cb6d-78ktc_kube-system" network: missing network name:, failed to clean up sandbox container "b17871cf37fec75d431480096c668f785d555f2b07d94ce1e699a9590d4f54e0" network for pod "coredns-6d4b75cb6d-78ktc": networkPlugin cni failed to teardown pod "coredns-6d4b75cb6d-78ktc_kube-system" network: missing network name]
  Normal   SandboxChanged          8s (x14 over 3m)  kubelet            Pod sandbox changed, it will be killed and re-created.

Manually bypass:

• after I append "name": "loopback" into the /etc/cni/net.d/200-loopback.conf, the pod could finally be created.

Attach the log file

log.txt

Operating System

macOS (Default)

Driver

Docker

[STRRL]

~~maybe related with https://github.com/containernetworking/plugins/issues/167~~

[STRRL]

I found that here is a mismatch between cri-o loopback config file and CNI spec, I have no idea why it works well before.

I create a PR for upstream: https://github.com/cri-o/cri-o/pull/6273

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.