failed: exec failed: container_linux.go:348: starting container process caused "exec: \"/bin/bash\": stat.../bin/bash: no such file or directory": unknown command terminated with exit code 126 [root@lydtest01...~]# 二、问题原因 最核心内容，没有找到/bin/bash这个执行文件，代表服务器没有安装bash脚本 "/bin/bash\": stat /bin/bash: no such file or...directory 一般的容器都可以执行/bin/bash，但也有部分容器没有，那么我们可以用/bin/sh来替换/bin/bash 三、解决问题 将bash登录方式，更换为sh登录 kubectl -
alpine docker exec: "/bin/bash": stat /bin/bash: no such file or directory 解决方案 docker exec -it 029e6df30836.../bin/bash exec: "/bin/bash": stat /bin/bash: no such file or directory 我们一般可能会在容器启动后进入容器，常用的是docker
docker exec -it 029e6df30836 /bin/bash exec: “/bin/bash”: stat /bin/bash: no such file or directory
mkswap /swap 激活swap空间 sudo mkswap /swap 第四步： sudo swapon /swap 要和上面的swap所对应不然就会报stat...of swapfile failed: No such file or directory sudo swapon /swap 最后 free -m
/var/lib/kubelet/config.yaml unable to load client CA file /etc/kubernetes/pki/ca.crt failed to run...Kubelet: unable to load bootstrap kubeconfig: stat /etc/kubernetes/bootstrap-kubelet.conf: no such file...or directory 背景：node 节点 kubeadm reset 后 重新kubeadm join失败 Failed to execute iptables-restore: exit status.../kubernetes/admin.conf Error from server (AlreadyExists): secrets “kubernetes-dashboard-certs” already...exists kubectl delete -f kubernetes-dashboard.yaml 重新apply The Service “kubernetes-dashboard” is invalid
6c76c8bb89-6krhq": networkPlugin cni failed to set up pod "coredns-6c76c8bb89-6krhq_kube-system" network: stat.../var/lib/calico/nodename: no such file or directory: check that the calico/node container is running...连接Node节点，使用以下命令删除node节点上关于calico的配置信息，并重启kubelet服务 rm -rf /etc/cni/net.d/* rm -rf /var/lib/cni/calico.../var/lib/calico/nodename: no such file or directory 这个错误，这个时候就发现了 是calico配置残留的问题，然后找到相关的calico文件删除掉问题就解决了...需要删除/var/lib/calico这个目录和/etc/cni/net.d/这个目录下的calico文件就行了 到这里问题就解决了 另外还有个问题就是calico/node is not ready
但我想在挂载目录时就映射到宿主机包含 POD_NAME 的目录下，于是就考虑 SubPathExpr，这个是 Kubernetes 1.17 后有的功能。...kubectl apply -f deployment.yaml 后，并没有成功运行起来， kubectl describe pod my-pod-xxx -n mynamespace 发现报错 Error: stat.../tmp/log: no such file or directory 非常地不解，也只好先加上 type: volumes: - name: log.../kubernetes/issues/61456 （实际上先搜到的是一个翻译文 ddeevv.com/question/kubernetes-kubernetes-61456.html） 原来是因为早期...v1 metadata: name: log-config namespace: development data: log.conf: >+ xxxxxx xxxxxx.File
报错如红色内容： tar: /root/jiangyu/projects/springCloud/clientOne/springcloud-clientOne: Cannot stat: No such...file or directory tar: Exiting with failure status due to previous errors ?
- --root-ca-file=/etc/kubernetes/pki/ca.crt - --service-account-private-key-file=/etc/kubernetes.../kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf" Environment="KUBELET_CONFIG_ARGS.../kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --pod-manifest-path=/etc...00:51:35 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=...00:00:02 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=
/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kub....../kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf" Environment="KUBELET_CONFIG_ARGS.../kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf，这里提到了两个配置文件 bootstrap-kubelet.conf...与 kubelet.conf，其中第一个文件不存在： ➜ cat /etc/kubernetes/bootstrap-kubelet.conf cat: /etc/kubernetes/bootstrap-kubelet.conf...Pods from directory "/etc/kubernetes/manifests".
/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kub....../kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf，这里提到了两个配置文件 bootstrap-kubelet.conf...与 kubelet.conf，其中第一个文件不存在： ➜ cat /etc/kubernetes/bootstrap-kubelet.conf cat: /etc/kubernetes/bootstrap-kubelet.conf...: No such file or directory 而第二个配置文件就是一个 kubeconfig 文件的格式，这个文件中就指定了 APIServer 的地址，可以看到还是之前的 IP 地址： ➜...y rm: remove regular file ‘/etc/kubernetes/pki/apiserver.key’?
08.552896 1651 removeetcdmember.go:79] [reset] No kubeadm config, using etcd pod spec to get data directory.../kubernetes/manifests /etc/kubernetes/pki] [reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes.../kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes...To do so, you must remove /etc/cni/net.d The reset process does not reset or clean up iptables rules...Please, check the contents of the $HOME/.kube/config file. [root@knode02 ~]#
/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf" Environment="KUBELET_CONFIG_ARGS...systemd --runtime-cgroups=/systemd/system.slice --kubelet-cgroups=/systemd/system.slice" # This is a file...KUBELET_EXTRA_ARGS should be sourced from this file..../kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf" Environment="KUBELET_CONFIG_ARGS...KUBELET_EXTRA_ARGS should be sourced from this file.
system): stat -c %a /etc/kubernetes/manifests/kube-apiserver.yaml In the output, check to ensure that...command based on the etcd data directory you found from the previous command: stat -c %a /var/lib/etcd...command based on the etcd data directory you found from the previous command: stat -c %U:%G /var/lib...Secure the Kubernetes PKI directory and file ownership....Secure the Kubernetes PKI directory and file permissions.
44.876393 9649 removeetcdmember.go:79] [reset] No kubeadm config, using etcd pod spec to get data directory.../kubernetes/manifests /etc/kubernetes/pki] [reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes.../kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes...Please, check the contents of the $HOME/.kube/config file. 4....] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env" [kubelet-start
=/etc/kubernetes/pki/etcd/peer.crt --peer-client-cert-auth=true --peer-key-file=/etc/kubernetes.../kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet...=10.244.0.0/16 --cluster-name=kubernetes --cluster-signing-cert-file=/etc/kubernetes/pki/...--port=0 --requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.crt --root-ca-file...=/etc/kubernetes/pki/ca.crt --service-account-private-key-file=/etc/kubernetes/pki/sa.key
with kubeadm and kubelet v1.11+ [Service] Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc.../kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf" Environment="KUBELET_CONFIG_ARGS...kubelet/config.yaml" Environment="KUBELET_CGROUP_ARGS=--cgroup-driver=systemd" #增加这一行 # This is a file...KUBELET_EXTRA_ARGS should be sourced from this file....EnvironmentFile=-/etc/sysconfig/kubelet ExecStart= ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS
安装过程比较慢，要等一下 kubectl apply -f https://docs.projectcalico.org/manifests/calico.yaml 问题 k8s network: stat.../var/lib/calico/nodename: no such file or directory 这些处理好之后我发现还是出现network: stat /var/lib/calico/nodename...: no such file or directory 这个错误，这个时候就发现了 是calico 配置残留的问题，然后找到相关的calico 文件删除掉问题就解决了 需要删除 /var/lib/calico...这个目录 和 /etc/cni/net.d/ 这个目录下的calico 文件就行了 删除以后删除原有pod 问题 子节点报 The connection to the server localhost.../kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config https://kubernetes.io
--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already...exists [ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/...[reset] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml...[/etc/kubernetes/manifests /etc/kubernetes/pki] [reset] deleting files: [/etc/kubernetes/admin.conf /...etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf
default-token-t8rfx (ro) Volumes: volumn-sls-15644718371690: Type: EmptyDir (a temporary directory...-bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf..." Environment="KUBELET_SYSTEM_PODS_ARGS=--pod-manifest-path=/etc/kubernetes/manifests" Environment="KUBELET_NETWORK_ARGS...=/etc/kubernetes/pki/ca.crt" Environment="KUBELET_CGROUP_ARGS=--system-reserved=memory=300Mi...<10%,nodefs.inodesFree<5% --cgroup-driver=systemd" Environment="KUBELET_CERTIFICATE_ARGS=--tls-cert-<em>file</em>
领取专属 10元无门槛券
手把手带您无忧上云
云服务器
ICP备案
对象存储
实时音视频
即时通信 IM
