[ERROR FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]: 问题解决

1320503165

( v: u* r; g' ?1 @. z0 g
0 T+ l1 e* A3 D  n0 |   [ERROR FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables does not exist
* s3 S' A5 P- x' r    [ERROR FileContent--proc-sys-net-ipv4-ip_forward]: /proc/sys/net/ipv4/ip_forward contents are not set to 1
4 C+ i. J  M8 U9 _; {: E

- D5 E  n9 `- j. V. F

4 ~$ f/ H  S- x# v[root@kubernetes-master net]# vim /etc/sysctl.d/k8s.conf
[root@kubernetes-master net]# modprobe br_netfilter
[root@kubernetes-master net]# sysctl --system /etc/sysctl.d/k8s.conf
* Applying /usr/lib/sysctl.d/00-system.conf ...
net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
  D" o, \$ ]! d. M; o2 G9 W2 G( h9 d* Applying /usr/lib/sysctl.d/10-default-yama-scope.conf ...
kernel.yama.ptrace_scope = 0
* Applying /usr/lib/sysctl.d/50-default.conf ...
0 S6 d4 |$ ^/ ~kernel.sysrq = 16
; d) O6 b+ w3 d2 Z. R" `kernel.core_uses_pid = 1
" h6 c; B( J- v. g9 r0 m$ skernel.kptr_restrict = 1
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
# ^/ P9 K0 _* r' }: e$ W8 Snet.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.all.accept_source_route = 0
6 I/ ?4 f5 ^# K0 I" L( M5 ^net.ipv4.conf.default.promote_secondaries = 1
net.ipv4.conf.all.promote_secondaries = 1
fs.protected_hardlinks = 1
fs.protected_symlinks = 1
* Applying /etc/sysctl.d/99-sysctl.conf ...
kernel.pid_max = 316448
% v9 G/ A6 c; m/ N+ @; H/ {* Applying /etc/sysctl.d/k8s.conf ...
net.bridge.bridge-nf-call-ip6tables = 1
7 J0 h$ g' o/ n. u1 i: `$ hnet.bridge.bridge-nf-call-iptables = 1
* Applying /etc/sysctl.conf ...
) n- j7 @( m6 J) Kkernel.pid_max = 316448
[root@kubernetes-master net]# kubeadm init --apiserver-advertise-address=192.168.8.190  --image-repository registry.aliyuncs.com/google_containers  --kubernetes-version v1.28.0 --service-cidr=10.177.100.0/12 --pod-network-cidr=10.233.0.0/16  --cri-socket=unix:///var/run/cri-dockerd.sock  
[init] Using Kubernetes version: v1.28.0
$ F  R/ W/ D8 W1 u6 S5 ^[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
: Q6 n5 X7 l+ v" [4 S* H    [ERROR CRI]: container runtime is not running: output: E0915 10:46:46.870746    2864 remote_runtime.go:616] "Status from runtime service failed" err="rpc error: code = Unavailable desc = connection closed before server preface received"
" B. m9 o3 Q. btime="2024-09-15T10:46:46+08:00" level=fatal msg="getting status of runtime: rpc error: code = Unavailable desc = connection closed before server preface received"
+ F+ u/ I! [( P( y% L) o9 W3 Z: ^/ M, error: exit status 1
    [ERROR FileContent--proc-sys-net-ipv4-ip_forward]: /proc/sys/net/ipv4/ip_forward contents are not set to 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
[root@kubernetes-master net]# docker ps
: m7 G+ u- [6 v$ H2 y2 w
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
[root@kubernetes-master net]#
[root@kubernetes-master net]# systemctl restart docker.service
[root@kubernetes-master net]# docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
( o" [+ B. Q, w* R& g' b, x' m6 b[root@kubernetes-master net]# systemctl enable docker.service
Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.
[root@kubernetes-master net]# systemctl status cri-docker.service
; K! V; C& Z1 G$ l; B* b1 e● cri-docker.service - CRI Interface for Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/cri-docker.service; enabled; vendor preset: disabled)
: L  o/ ]$ Z8 x! p* ]   Active: failed (Result: start-limit) since Sun 2024-09-15 10:46:51 CST; 1min 37s ago
. X3 `: @  P- F( m8 M5 |% _, q# q     Docs: https://docs.mirantis.com
Main PID: 2909 (code=exited, status=1/FAILURE)
% f3 G+ q9 t! ^! d2 Y; X
Sep 15 10:46:49 kubernetes-master systemd[1]: Failed to start CRI Interface for Docker Application C...ne.
Sep 15 10:46:49 kubernetes-master systemd[1]: Unit cri-docker.service entered failed state.
; C$ m2 g( T) h& WSep 15 10:46:49 kubernetes-master systemd[1]: cri-docker.service failed.
Sep 15 10:46:51 kubernetes-master systemd[1]: cri-docker.service holdoff time over, scheduling restart.
Sep 15 10:46:51 kubernetes-master systemd[1]: Stopped CRI Interface for Docker Application Container...ne.
) S% Q% i2 @9 N( L6 {/ I1 |Sep 15 10:46:51 kubernetes-master systemd[1]: start request repeated too quickly for cri-docker.service
) t7 }  C: o, B* n: c7 J& e3 hSep 15 10:46:51 kubernetes-master systemd[1]: Failed to start CRI Interface for Docker Application C...ne.
Sep 15 10:46:51 kubernetes-master systemd[1]: Unit cri-docker.service entered failed state.
Sep 15 10:46:51 kubernetes-master systemd[1]: cri-docker.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
/ Y" M, N& L! t4 L: N[root@kubernetes-master net]# systemctl restart cri-docker.service
[root@kubernetes-master net]# systemctl status cri-docker.service
+ F$ w6 Q3 W+ k4 w( Y% \0 o● cri-docker.service - CRI Interface for Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/cri-docker.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2024-09-15 10:48:38 CST; 1s ago
) R# G' S# x. m' l     Docs: https://docs.mirantis.com
Main PID: 3339 (cri-dockerd)
* R  ^! d& C- ^    Tasks: 8
. _) |0 [: K' Q+ a4 N" U   Memory: 16.2M
   CGroup: /system.slice/cri-docker.service
           └─3339 /usr/bin/cri-dockerd --container-runtime-endpoint fd:// --pod-infra-container-image=r...
- T) m8 \3 o: ?, s7 @* @# O
3 \+ ?$ l6 j! U0 F, U. l; fSep 15 10:48:38 kubernetes-master cri-dockerd[3339]: time="2024-09-15T10:48:38+08:00" level=info msg...0s"
Sep 15 10:48:38 kubernetes-master cri-dockerd[3339]: time="2024-09-15T10:48:38+08:00" level=info msg...ne"
Sep 15 10:48:38 kubernetes-master cri-dockerd[3339]: time="2024-09-15T10:48:38+08:00" level=info msg...ni"
- U& D/ i+ y( m) u0 WSep 15 10:48:38 kubernetes-master cri-dockerd[3339]: time="2024-09-15T10:48:38+08:00" level=info msg...ni"
Sep 15 10:48:38 kubernetes-master cri-dockerd[3339]: time="2024-09-15T10:48:38+08:00" level=info msg...ive
Sep 15 10:48:38 kubernetes-master cri-dockerd[3339]: time="2024-09-15T10:48:38+08:00" level=info msg...fs"
& _" O- [, i8 vSep 15 10:48:38 kubernetes-master systemd[1]: Started CRI Interface for Docker Application Container...ne.
Sep 15 10:48:38 kubernetes-master cri-dockerd[3339]: time="2024-09-15T10:48:38+08:00" level=info msg...,}"
Sep 15 10:48:38 kubernetes-master cri-dockerd[3339]: time="2024-09-15T10:48:38+08:00" level=info msg...e."
& @. E3 v5 Q: b( z% g6 SSep 15 10:48:38 kubernetes-master cri-dockerd[3339]: time="2024-09-15T10:48:38+08:00" level=info msg...nd"
Hint: Some lines were ellipsized, use -l to show in full.
. O% D5 m( O- S$ U% M
+ o; D5 e6 a% F% L7 i

1320503165

[root@kubernetes-master net]# kubeadm init --apiserver-advertise-address=192.168.8.190  --image-repository registry.aliyuncs.com/google_containers  --kubernetes-version v1.28.0 --service-cidr=10.177.100.0/12 --pod-network-cidr=10.233.0.0/16  --cri-socket=unix:///var/run/cri-dockerd.sock  
- b6 o7 Z+ t* J2 L/ J[init] Using Kubernetes version: v1.28.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
8 v$ Z5 Z4 u# o+ P[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
% d9 N  |7 R1 @' |

也就是说docker未启动就会报错