kind: [PODMAN] kind cluster creation fails on podman using Debian 11; identified a workaround to prevent clusterfail.

Kind cluster creation failed on Podman (rootful) using Debian GNU/Linux 11 :

Kind to create multi-node cluster without errors on Podman using Debian:

Steps to Reproduce:

I am using kind 0.12.0 on Debian 11.

I have a kind config yaml file :

kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
featureGates:
  "SetHostnameAsFQDN": true
networking:
  ipFamily: ipv4
  kubeProxyMode: "iptables"
nodes:
- role: control-plane
  image: kindest/node:v1.23.0@sha256:49824ab1727c04e56a21a5d8372a402fcd32ea51ac96a2706a12af38934f81ac
- role: worker
  image: kindest/node:v1.23.0@sha256:49824ab1727c04e56a21a5d8372a402fcd32ea51ac96a2706a12af38934f81ac
- role: worker
  image: kindest/node:v1.23.0@sha256:49824ab1727c04e56a21a5d8372a402fcd32ea51ac96a2706a12af38934f81ac

I am trying to create a kind cluster on debian 11 using podman 3.0.1 using below command.

sudo kind create cluster --name ko2 --config /home/debuggerboy/labs/kubernetes/anish-kind/multi-node.yaml

The above command takes a lot of time and then fails with below error:

Full Error : https://gist.github.com/debuggerboy/e7ec918dd984cdbe9e8c1963393d2fe2#file-kind-sigs-cluster-creation-error-txt

Additional details with regards to this error:

After hours of debugging and mutiple attempts, I was able to prevent the kind cluster from failing.

I created an inject script : https://gist.github.com/debuggerboy/e7ec918dd984cdbe9e8c1963393d2fe2#file-podman-fix-for-cluster-fail-sh

I execute the above inject script a few seconds after the kind create cluster is invoked.

This will prevent the kind cluster on podman from failing.

Environment:

  • kind version: kind v0.12.0 go1.17.8 linux/amd64
  • Kubernetes version:
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.1", GitCommit:"86ec240af8cbd1b60bcc4c03c20da9b98005b92e", GitTreeState:"clean", BuildDate:"2021-12-16T11:41:01Z", GoVersion:"go1.17.5", Compiler:"gc", Platform:"linux/amd64"}
The connection to the server 127.0.0.1:46667 was refused - did you specify the right host or port?
  • Docker version: not applicable
  • Podman version:
Version:      3.0.1
API Version:  3.0.0
Go Version:   go1.15.9
Built:        Thu Jan  1 05:30:00 1970
OS/Arch:      linux/amd64
  • OS (e.g. from /etc/os-release):
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Please see : https://gist.github.com/debuggerboy/e7ec918dd984cdbe9e8c1963393d2fe2

Note: I am not having much experience in kubernetes, please kindly ignore if this report does not qualify as a bug. My apologies

Thanks debuggerboy

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15 (9 by maintainers)

Most upvoted comments

Podman >= 4.0 fixes this issue. I’ve tested using podman v4

aardvark-dns 1.3.0-1
netavark 1.1.0-1
podman 4.1.1-2

Verify if your podman network backend is cni

podman info --format {{.Host.NetworkBackend}}
cni

If it is set to cni the fix for this issue is to change the network backend to aardvark See the man page for man containers.conf Search network_backend to understand how to change the network backend to aardvark

You can leave the cni-plugins pkg installed, podman will obey the containers.conf configuration.

@debuggerboy podman community should be answer that question better than us https://github.com/containers/podman

Hi @debuggerboy , If version is not a constrain here do you mind trying this with podman 4.0.0-dev or even better something from upstream. I am unable to reproduce this issue with 4.0.0-dev from upstream and my network stack is netavark/aardvark-dns but it should work with CNI as well.

why is podman creating the hosts entries with ipv6?

fc00:f853:ccd:e793::93 ko2-control-plane ko2-control-plane

that is the problem,