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

1320503165

- z# j3 d/ p( h! C* p' p
5 Z& [+ D3 {5 S6 f4 }1 j# b   [ERROR FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables does not exist
    [ERROR FileContent--proc-sys-net-ipv4-ip_forward]: /proc/sys/net/ipv4/ip_forward contents are not set to 1

- t$ k& ^3 W' y


: k4 y/ b7 v) R[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
! E1 P  \2 h* A2 D! q* Applying /usr/lib/sysctl.d/00-system.conf ...
net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
% K/ d. `) d4 l; anet.bridge.bridge-nf-call-arptables = 0
* Applying /usr/lib/sysctl.d/10-default-yama-scope.conf ...
kernel.yama.ptrace_scope = 0
* Applying /usr/lib/sysctl.d/50-default.conf ...
/ }2 H; a3 ^* J8 h& Okernel.sysrq = 16
7 C) j3 O' G, O4 ckernel.core_uses_pid = 1
kernel.kptr_restrict = 1
7 x7 [! V/ `( c% q  Ynet.ipv4.conf.default.rp_filter = 1
3 `& ^- X5 d2 t9 S& V* ^" _net.ipv4.conf.all.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.all.accept_source_route = 0
net.ipv4.conf.default.promote_secondaries = 1
7 {. n1 _% e" [0 Pnet.ipv4.conf.all.promote_secondaries = 1
fs.protected_hardlinks = 1
fs.protected_symlinks = 1
* Applying /etc/sysctl.d/99-sysctl.conf ...
! L) d1 @6 o: Skernel.pid_max = 316448
/ K6 f( ]" g+ i1 z5 S' B3 T* k* Applying /etc/sysctl.d/k8s.conf ...
net.bridge.bridge-nf-call-ip6tables = 1
0 V& ?4 w  r& l* v+ Z5 }: V% Pnet.bridge.bridge-nf-call-iptables = 1
$ N) h% M/ K) |( V& r+ G* Applying /etc/sysctl.conf ...
$ t! Z5 }' |" R( Dkernel.pid_max = 316448
5 Q  g+ O5 P+ c* U# O$ o8 G[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
/ ?. Q9 f5 ?  Q[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
" g$ U& h* x2 z: l8 d  b/ }& G    [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"
7 j$ V9 h% b0 n8 P. s. 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"
, 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

" A/ A2 F, {/ K# g6 dCannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
[root@kubernetes-master net]#
" d4 w; a! W. ?# k* k, n[root@kubernetes-master net]# systemctl restart docker.service
* J1 M0 w/ B% G; q[root@kubernetes-master net]# docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
[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
" P+ f1 u; B  J● cri-docker.service - CRI Interface for Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/cri-docker.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Sun 2024-09-15 10:46:51 CST; 1min 37s ago
+ |' c; c* ^' m* B8 K     Docs: https://docs.mirantis.com
. i" p/ w* l3 Z. E% o- c Main PID: 2909 (code=exited, status=1/FAILURE)

$ R; M+ R5 f5 E* z* y4 z) |Sep 15 10:46:49 kubernetes-master systemd[1]: Failed to start CRI Interface for Docker Application C...ne.
% q: U3 J" A  X2 j2 h8 ISep 15 10:46:49 kubernetes-master systemd[1]: Unit cri-docker.service entered failed state.
1 q9 b* R, O) \& U9 m! K6 ZSep 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.
8 f. r, K, M# K- uSep 15 10:46:51 kubernetes-master systemd[1]: start request repeated too quickly for cri-docker.service
( C  o+ K: w# x3 Y; p* `Sep 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.
0 V, E; k4 D( @3 ]; _, nSep 15 10:46:51 kubernetes-master systemd[1]: cri-docker.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
) N5 h" F( Q, c[root@kubernetes-master net]# systemctl restart cri-docker.service
$ |- ^1 b! e6 K( I( i& x; H[root@kubernetes-master net]# systemctl status cri-docker.service
% D6 ]  I( J- S* d6 ~" Y● cri-docker.service - CRI Interface for Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/cri-docker.service; enabled; vendor preset: disabled)
- `1 y% o! I: v' g6 M! M   Active: active (running) since Sun 2024-09-15 10:48:38 CST; 1s ago
% u$ ?4 B+ r6 c$ k& B: h     Docs: https://docs.mirantis.com
Main PID: 3339 (cri-dockerd)
& V: i6 G5 p& H1 H! i    Tasks: 8
# G- @: o7 J' q  H# b   Memory: 16.2M
   CGroup: /system.slice/cri-docker.service
           └─3339 /usr/bin/cri-dockerd --container-runtime-endpoint fd:// --pod-infra-container-image=r...
4 M7 u$ W2 h/ I' R
$ |( O  A6 ~  K# W* i' J3 {  RSep 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"
Sep 15 10:48:38 kubernetes-master cri-dockerd[3339]: time="2024-09-15T10:48:38+08:00" level=info msg...ni"
: x' F9 f6 M3 xSep 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"
8 I  t! E4 X4 X7 k. b2 r+ [Sep 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."
Sep 15 10:48:38 kubernetes-master cri-dockerd[3339]: time="2024-09-15T10:48:38+08:00" level=info msg...nd"
6 c' p" t$ Q4 c/ v+ A7 j2 I& U  rHint: Some lines were ellipsized, use -l to show in full.

- X& I. b. B; q

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  
5 n$ `, z9 t$ N[init] Using Kubernetes version: v1.28.0
[preflight] Running pre-flight checks
3 m  }6 [5 M' F. |% ]3 c[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
, H9 t8 F7 }5 n# P0 S[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
' ~4 Y0 T0 ]3 `9 D; [+ X1 M% @
: i. m$ y4 d* G6 {# c% p& \" ?
3 G8 M  D* R- h1 ^( B7 M也就是说docker未启动就会报错