panic: runtime error: invalid memory address or nil pointer dereference when use kubeadm
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 692
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When I try to do the "kubeadm init" command to initialize the first node of a kubernetes cluster, I get the following error.
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x74d0aa]
goroutine 1 [running]:
k8s.io/kubernetes/vendor/github.com/modern-go/reflect2.(*frozenConfig).Type2(0x189ee20, {0x1db32d0, 0x17f4dc0})
Reproduction steps
1. install kubeadm with tdnf install kubernetes-kubeadm
2. run "kubeadm init"
Expected behavior
The kubeadm command should finish and my cluster should be initialized.
Additional context
new installation of photonOS on a vmware VM (ESXi 7.0 U2 (VM version 19))
VMware Photon OS 4.0
PHOTON_BUILD_NUMBER=2f5aad892
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with the listed tdnf installation and the kubeadm init entry point on VMware Photon OS 4.0. Use the reported panic and kubelet-start output to trace the failing component; done means kubeadm init finishes and the first cluster node is initialized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, linux
- Domain
- infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100