Kubernetes 企业代理背后的kubeadm init

我尝试在具有自己ca的企业代理之后建立kubernetes集群。
我基本上遵循了以下教程：

另外，我还做了以下工作来支持我们的企业网络

• 我在env中设置了：http\u proxy https\u proxy no\u proxy
• 我将代理添加到 /etc/apt/apt.conf
• 我在/usr/local/share/CA证书中安装了CA文件（并运行更新CA证书）
• 我将代理配置添加到docker systemd守护程序（重新加载守护程序并重新启动docker）

现在，当我尝试使用kubeadm init时，会发生以下情况：

[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
I1111 22:00:24.471496    5900 checks.go:845] pulling k8s.gcr.io/kube-apiserver:v1.16.2
I1111 22:00:40.105465    5900 checks.go:845] pulling k8s.gcr.io/kube-controller-manager:v1.16.2
I1111 22:00:50.804949    5900 checks.go:845] pulling k8s.gcr.io/kube-scheduler:v1.16.2
I1111 22:00:56.139481    5900 checks.go:845] pulling k8s.gcr.io/kube-proxy:v1.16.2
I1111 22:01:01.264787    5900 checks.go:845] pulling k8s.gcr.io/pause:3.1
I1111 22:01:02.420756    5900 checks.go:845] pulling k8s.gcr.io/etcd:3.3.15-0
I1111 22:01:22.864754    5900 checks.go:845] pulling k8s.gcr.io/coredns:1.6.2
[preflight] Some fatal errors occurred:
        [ERROR ImagePull]: failed to pull image k8s.gcr.io/coredns:1.6.2: output: 1.6.2: Pulling from coredns
c6568d217a00: Pulling fs layer
3970bc7cbb16: Pulling fs layer
c6568d217a00: Verifying Checksum
3970bc7cbb16: Verifying Checksum
3970bc7cbb16: Download complete
filesystem layer verification failed for digest sha256:c6568d217a0023041ef9f729e8836b19f863bcdb612bb3a329ebc165539f5a80
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
error execution phase preflight
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run.func1
        /workspace/anago-v1.16.2-beta.0.19+c97fe5036ef3df/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:237
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).visitAll
        /workspace/anago-v1.16.2-beta.0.19+c97fe5036ef3df/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:424
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run
        /workspace/anago-v1.16.2-beta.0.19+c97fe5036ef3df/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:209
k8s.io/kubernetes/cmd/kubeadm/app/cmd.NewCmdInit.func1
        /workspace/anago-v1.16.2-beta.0.19+c97fe5036ef3df/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/init.go:146
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).execute
        /workspace/anago-v1.16.2-beta.0.19+c97fe5036ef3df/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:830
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).ExecuteC
        /workspace/anago-v1.16.2-beta.0.19+c97fe5036ef3df/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:914
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).Execute
        /workspace/anago-v1.16.2-beta.0.19+c97fe5036ef3df/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:864
k8s.io/kubernetes/cmd/kubeadm/app.Run
        /workspace/anago-v1.16.2-beta.0.19+c97fe5036ef3df/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/kubeadm.go:50
main.main
        _output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/kubeadm.go:25
runtime.main
        /usr/local/go/src/runtime/proc.go:200
runtime.goexit
        /usr/local/go/src/runtime/asm_amd64.s:1337

有人有主意吗

---

操作系统：Ubuntu18.04.3 LTS

你有这个kubeadm是云端的还是裸机的？你也看到了吗？我看到了，它的意思是“我将代理配置添加到docker systemd守护程序（重新加载守护程序并重新启动docker）”。Docker pull可以毫无问题地工作。它是“在云端”-->proxmox。我试着按照这个指令去做，但它对我不起作用。您是否尝试过从以下文档安装docker：以及以后基于官方文档的

kubeadm

：以及kubeadm init？它通过调度程序、apiserver和代理，但在coredns上停止。你也可以附加你的配置文件被改变了吗？我发现了错误。我们的代理阻止了一些小图层文件。