[root@localhost ~]# cat /etc/redhat-release
CentOS Linux release 7.6.1810 (AltArch)
[root@localhost ~]#
[root@localhost ~]# hostnamectl
Static hostname: localhost.localdomain
Transient hostname: localhost
Icon name: computer-vm
Chassis: vm
Machine ID: 65a539173aca43bca524c9829d298907
Boot ID: 1e1074e1bf9b466c8c44774276cfd8c5
Virtualization: kvm
Operating System: CentOS Linux 7 (AltArch)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 4.14.0-115.el7a.0.1.aarch64
Architecture: arm64
[root@localhost ~]#
[root@localhost ~]# yum -y install kubeadm-1.19.2-0.aarch64 kubectl-1.19.2-0.aarch64 kubelet-1.19.2-0.aarch64
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
Resolving Dependencies
--> Running transaction check
---> Package kubeadm.aarch64 0:1.19.2-0 will be installed
--> Processing Dependency: kubernetes-cni >= 0.8.6 for package: kubeadm-1.19.2-0.aarch64
--> Processing Dependency: cri-tools >= 1.13.0 for package: kubeadm-1.19.2-0.aarch64
---> Package kubectl.aarch64 0:1.19.2-0 will be installed
---> Package kubelet.aarch64 0:1.19.2-0 will be installed
--> Processing Dependency: socat for package: kubelet-1.19.2-0.aarch64
--> Processing Dependency: conntrack for package: kubelet-1.19.2-0.aarch64
--> Running transaction check
---> Package cri-tools.aarch64 0:1.13.0-0 will be installed
---> Package kubelet.aarch64 0:1.19.2-0 will be installed
--> Processing Dependency: socat for package: kubelet-1.19.2-0.aarch64
--> Processing Dependency: conntrack for package: kubelet-1.19.2-0.aarch64
---> Package kubernetes-cni.aarch64 0:0.8.7-0 will be installed
--> Finished Dependency Resolution
Error: Package: kubelet-1.19.2-0.aarch64 (kubernetes)
Requires: socat
Error: Package: kubelet-1.19.2-0.aarch64 (kubernetes)
Requires: conntrack
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
[root@localhost ~]#
I’d like to know how to solve the Error, could you please help me?
Hi @striver619, we’re having a triage session and reviewed this issue. We’d like to help you find a way to solve this. Are you still interested? If so, @Verolop is happy to work with you. Please let us know, and sorry for the delay in response.