@TOC
参考资料|网址
K8S和Docker介绍
装置计划参考
k8s拉取镜像解决方案
官网文档
dockerHub
虚拟化
Minikube测试教程
装置攻略
前言
装置环境是云服务器，Ubuntu18的零碎，无奈采纳虚拟机那种模式。
装置目标次要是为了学习，所以抉择了Minikube。
生成环境版，之后兴许也会出一个教程，但临时还不想就义本人服务器的swap分区，所以见谅啦。
Minikube
MiniKube是K8S官网为了凋谢者能在个人电脑上运行K8S提供的一套工具。
由Go语言实现，通过调用虚拟化管理程序，创立出一个运行在虚拟机内的单点集群。
装置kubectl
K8S集群是典型的C/S架构，有一个官网提供的名为kubectl的CLI工具。
尽量保障kubectl版本和K8S集群版本保持一致，或版本相差在一个小版本内。
能够抉择指定版本，也能够间接抉择装置最新的。
这个是指定版本：
curl -LO https://dl.k8s.io/release/v1.10.7/bin/linux/amd64/kubectl
curl -LO https://dl.k8s.io/v1.10.7/bin/linux/amd64/kubectl.sha256
echo "$(<kubectl.sha256) kubectl" | sha256sum --check -c
可能会遇到如上谬误，按如下解决即可：
install -o root -g root -m 0755 kubectl /usr/local/bin/kubectl
装置最新版本
官网文档
curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"curl -LO "https://dl.k8s.io/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl.sha256"echo "$(<kubectl.sha256) kubectl" | sha256sum --check装置Minikube
先看，不要焦急操作！
- wget -O minikube https://github.com/kubernetes...
- chmod +x minikube 赋予执行权限
- sudo mv minikube /usr/local/bin/minikube
- /usr/local/bin/minikube version
minikube version: v0.28.2
# 装置最新的:curl -Lo minikube https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64chmod +x minikubesudo cp ./minikube /usr/local/bin/minikube应用 Minikube 创立集群，只有简略的执行 minikube start 即可
root@VM-0-11-ubuntu:/dbroot/NNroot# minikube startStarting local Kubernetes v1.10.0 cluster...Starting VM...E0709 16:38:40.267790 7566 start.go:174] Error starting host: Error creating host: Error executing step: Running precreate checks.: VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path. Retrying.E0709 16:38:40.268011 7566 start.go:180] Error starting host: Error creating host: Error executing step: Running precreate checks.: VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path================================================================================An error has occurred. Would you like to opt in to sending anonymized crashinformation to minikube to help prevent future errors?To opt out of these messages, run the command: minikube config set WantReportErrorPrompt false================================================================================Please enter your response [Y/n]:YE0709 16:38:48.449769 7566 util.go:151] Error uploading error message: : Post https://clouderrorreporting.googleapis.com/v1beta1/projects/k8s-minikube/events:report?key=AIzaSyACUwzG0dEPcl-eOgpDKnyKoUFgHdfoFuA: read tcp 172.17.0.11:41168->172.217.160.74:443: read: connection reset by peerError starting host: Error creating host: Error executing step: Running precreate checks.: VBoxManage not found.
因为没有应用虚拟机，应该将 Minikube 的 --vm-driver 参数设置为 none ，并且在本机曾经正确装置 Docker。 这种形式是无需虚拟化反对的。minikube start --vm-driver=none
root@VM-0-11-ubuntu:/dbroot/NNroot# minikube start --vm-driver=noneStarting local Kubernetes v1.10.0 cluster...Starting VM...Getting VM IP address...Moving files into cluster...Downloading kubeadm v1.10.0Downloading kubelet v1.10.0Finished Downloading kubeadm v1.10.0Finished Downloading kubelet v1.10.0Setting up certs...Connecting to cluster...Setting up kubeconfig...Starting cluster components...E0709 17:15:00.768230 21541 start.go:300] Error starting cluster: kubeadm init errorsudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors= DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data- minikube --ignore-preflight-errors=Port-10250 --ignore-preflight-errors=FileAvailabl e--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvaila ble--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvai lable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-erro rs=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap --ignore-preflight-errors=CRI &&sudo /usr/bin/kubeadm alpha phase addon kube-dns running command: : running command:sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors= DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data- minikube --ignore-preflight-errors=Port-10250 --ignore-preflight-errors=FileAvailabl e--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvaila ble--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvai lable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-erro rs=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap --ignore-preflight-errors=CRI &&sudo /usr/bin/kubeadm alpha phase addon kube-dns output: [init] Using Kubernetes version: v1.10.0[init] Using Authorization modes: [Node RBAC][preflight] Running pre-flight checks.[preflight] The system verification failed. Printing the output from the verificatio n:KERNEL_VERSION: 4.15.0-118-genericCONFIG_NAMESPACES: enabledCONFIG_NET_NS: enabledCONFIG_PID_NS: enabledCONFIG_IPC_NS: enabledCONFIG_UTS_NS: enabledCONFIG_CGROUPS: enabledCONFIG_CGROUP_CPUACCT: enabledCONFIG_CGROUP_DEVICE: enabledCONFIG_CGROUP_FREEZER: enabledCONFIG_CGROUP_SCHED: enabledCONFIG_CPUSETS: enabledCONFIG_MEMCG: enabledCONFIG_INET: enabledCONFIG_EXT4_FS: enabledCONFIG_PROC_FS: enabledCONFIG_NETFILTER_XT_TARGET_REDIRECT: enabled (as module)CONFIG_NETFILTER_XT_MATCH_COMMENT: enabled (as module)CONFIG_OVERLAY_FS: enabled (as module)CONFIG_AUFS_FS: enabled (as module)CONFIG_BLK_DEV_DM: enabledDOCKER_VERSION: 20.10.0OS: LinuxCGROUPS_CPU: enabledCGROUPS_CPUACCT: enabledCGROUPS_CPUSET: enabledCGROUPS_DEVICES: enabledCGROUPS_FREEZER: enabledCGROUPS_MEMORY: enabled [WARNING Hostname]: hostname "minikube" could not be reached [WARNING Hostname]: hostname "minikube" lookup minikube on 127.0.0.53:53: se rver misbehaving [WARNING FileExisting-crictl]: crictl not found in system pathSuggestion: go get github.com/kubernetes-incubator/cri-tools/cmd/crictlFlag --admission-control has been deprecated, Use --enable-admission-plugins or --di sable-admission-plugins instead. Will be removed in a future version.[preflight] Some fatal errors occurred: [ERROR SystemVerification]: unsupported docker version: 20.10.0[preflight] If you know what you are doing, you can make a check non-fatal with `--i gnore-preflight-errors=...`: running command:sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors= DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data- minikube --ignore-preflight-errors=Port-10250 --ignore-preflight-errors=FileAvailabl e--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvaila ble--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvai lable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-erro rs=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap --ignore-preflight-errors=CRI &&sudo /usr/bin/kubeadm alpha phase addon kube-dns.: exit status 2E0709 17:15:30.768922 21541 util.go:151] Error uploading error message: : Post https://clouderrorreporting.googleapis.com/v1beta1/projects/k8s-minikube/events:report?key=AIzaSyACUwzG0dEPcl-eOgpDKnyKoUFgHdfoFuA: dial tcp 172.217.160.74:443: i/o timeout如同Docker的版本太高了，是20的。
尝试升高版本
sudo systemctl stop dockersudo apt-get remove -y docker-ce docker-ce-clisudo apt-get updatesudo apt-get install -y docker-ce=5:18.09.4~3-0~ubuntu-bionic docker-ce-cli=5:18.09.4~3-0~ubuntu-bionicdocker versionsudo systemctl stop dockersudo apt-get remove -y docker-ce docker-ce-clisudo apt-get updatesudo apt-get install -y apt-transport-https ca-certificates curl software-properties-commoncurl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -sudo apt-get install -y docker-ce=17.12.0~ce-0~ubuntu docker-ce-cli=17.12.0~ce-0~ubuntudocker versionapt-get install docker-ce=17.03.0~ce-0~ubuntu docker-ce-cli=17.03.0~ce-0~ubuntu发现折腾来折腾去反而导致我Docker装不上了。
人生苦短，我抉择疾速装置，我要装回我本来高版本的Docker。
curl -fsSL https://get.docker.com | bash -s docker --mirror Aliyun如果遇到apt_pkg的谬误
1、进入包文件目录
cd /usr/lib/python3/dist-packages/
Select CodeCopy
2、执行软连贯
ln -s apt_pkg.cpython-36m-x86_64-linux-gnu.so apt_pkg.so
Select CodeCopy
如果apt_pkg.so已存在，则应用：
ln -fs apt_pkg.cpython-36m-x86_64-linux-gnu.so apt_pkg.so
Select CodeCopy
或者能够应用：
apt install python3-apt
cd /usr/lib/python3/dist-packages
cp apt_pkg.cpython-35m-x86_64-linux-gnu.so apt_pkg.cpython-36m-x86_64-linux-gnu.so
add-apt-repository "deb [arch=amd64] https://download.docker.com/l... xenial stable"
如果遇到cgroupfs的谬误
参考了这位大佬的博客进行了解决：
在/etc/docker下创立daemon.json并编辑：
mkdir /etc/docker/daemon.json
退出以下内容：
{
"exec-opts":["native.cgroupdriver=systemd"]
}
我要用最新的！
事实证明用旧的版本不如用新的，重来，从Docker开始全副都升到新的！
这是从新来过的后果：
我的服务器是双核的，如果你是单核可能还要再设置一下。
单核 cpu配置请设置 1
sudo minikube start --driver=none \
--extra-config=kubeadm.ignore-preflight-errors=NumCPU \ --force --cpus 1 \ --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers还是遇到了镜像的问题
试了如下形式通通不行，太苦楚了
- minikube start --driver=none --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers
- minikube start --driver=none --registry-mirror=https://dockerhub.azk8s.cn --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers
设置了image-repository齐全不起作用！
以下是具体谬误：
[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/doc s/setup/cri/error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.21.2: output : Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled whil e waiting for connection (Client.Timeout exceeded while awaiting headers), error: exit status 1 [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-controller-manager:v1.21. 2: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canc eled while waiting for connection (Client.Timeout exceeded while awaiting headers), error: exit status 1 [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-scheduler:v1.21.2: output : Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled whil e waiting for connection (Client.Timeout exceeded while awaiting headers), error: exit status 1 [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-proxy:v1.21.2: output: Er ror response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while wa iting for connection (Client.Timeout exceeded while awaiting headers), error: exit status 1 [ERROR ImagePull]: failed to pull image k8s.gcr.io/pause:3.4.1: output: Error res ponse from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting f or connection (Client.Timeout exceeded while awaiting headers), error: exit status 1 [ERROR ImagePull]: failed to pull image k8s.gcr.io/etcd:3.4.13-0: output: Error r esponse from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers), error: exit status 1 [ERROR ImagePull]: failed to pull image k8s.gcr.io/coredns/coredns:v1.8.0: output : Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled whil e waiting for connection (Client.Timeout exceeded while awaiting headers), error: exit status 1[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore -preflight-errors=...`To see the stack trace of this error execute with --v=5 or higher脚本解决镜像问题！
因为国内镜像问题，导致了下面一系列的ERROR。
写脚本从DockerHub的其余仓库里拉取镜像。
去DockerHub搜寻kube_proxy、kube_kube-apiserver等等。
就是上图报错中我框出来的这些货色。
向上面这样搜寻：
vim pull_k8s_images.sh内容：
set -o errexitset -o nounsetset -o pipefailKUBE_VERSION=v1.21.2KUBE_PAUSE_VERSION=3.4.1ETCD_VERSION=3.4.13-0DNS_VERSION=v1.8.0GCR_URL=k8s.gcr.io## k8smx这个你能够换DOCKERHUB_URL=k8smximages=(kube-proxy:${KUBE_VERSION}kube-scheduler:${KUBE_VERSION}kube-controller-manager:${KUBE_VERSION}kube-apiserver:${KUBE_VERSION}pause:${KUBE_PAUSE_VERSION}etcd:${ETCD_VERSION}coredns:${DNS_VERSION})for imageName in ${images[@]} ; do docker pull $DOCKERHUB_URL/$imageName docker tag $DOCKERHUB_URL/$imageName $GCR_URL/$imageName docker rmi $DOCKERHUB_URL/$imageNamedone授予执行权
chmod +x ./pull_k8s_images.sh执行
./pull_k8s_images.sh你能够查看本人曾经有了哪些镜像：
docker images
比如说我框出来的这些，就和ERROR的内容是匹配的
如果你发现还有镜像没有拉下来的，能够再写一个脚本，独自解决。
比如说coredns=v1.8.0没拉下来 :
set -o errexitset -o nounsetset -o pipefailDNS_VERSION=v1.8.0GCR_URL=k8s.gcr.io/corednsDOCKERHUB_URL=gotok8simages=(coredns:${DNS_VERSION})for imageName in ${images[@]} ; do docker pull $DOCKERHUB_URL/$imageName docker tag $DOCKERHUB_URL/$imageName $GCR_URL/$imageName docker rmi $DOCKERHUB_URL/$imageNamedone应用形式和下面是一样的。
k8smx、gotok8s都是本人能够选的，这个仓库不行就换一个。
拿到所有镜像后，minikube start --driver=none
曾经OK了。