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

1320503165

$ }: ]0 y$ ]+ }   [ERROR FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables does not exist
, T3 U( X- l7 V' d    [ERROR FileContent--proc-sys-net-ipv4-ip_forward]: /proc/sys/net/ipv4/ip_forward contents are not set to 1
# X1 F8 {, B" F
5 [( l9 M$ G+ ^0 w7 x  D
1 V, i: y9 e6 c$ `0 q

[root@kubernetes-master net]# vim /etc/sysctl.d/k8s.conf
9 V0 X: g8 f3 O$ ?$ }% a[root@kubernetes-master net]# modprobe br_netfilter
[root@kubernetes-master net]# sysctl --system /etc/sysctl.d/k8s.conf
( T- A+ N8 ~( {, z* Applying /usr/lib/sysctl.d/00-system.conf ...
# ^, C" p4 f9 k# G3 p" ?net.bridge.bridge-nf-call-ip6tables = 0
5 y% w& Y4 X3 l/ ~- F$ Anet.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
, C6 M! F( z' p% X5 p- @5 ~* Applying /usr/lib/sysctl.d/10-default-yama-scope.conf ...
kernel.yama.ptrace_scope = 0
2 h6 W5 N- X; o) C1 _4 s0 K* f* Applying /usr/lib/sysctl.d/50-default.conf ...
' k' d" m0 Q. g' W; E: j; {7 x5 tkernel.sysrq = 16
# H& q. r5 y- Q; b7 R: g% v+ lkernel.core_uses_pid = 1
. [( i% M* Y4 bkernel.kptr_restrict = 1
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
4 u1 Q" Y6 R3 B5 V2 bnet.ipv4.conf.default.accept_source_route = 0
* Q& a5 p+ r$ |net.ipv4.conf.all.accept_source_route = 0
5 ^7 U) r& f7 f% w+ hnet.ipv4.conf.default.promote_secondaries = 1
net.ipv4.conf.all.promote_secondaries = 1
fs.protected_hardlinks = 1
' v' Y. F. B  |2 I( xfs.protected_symlinks = 1
* Applying /etc/sysctl.d/99-sysctl.conf ...
0 r' n% l  ]7 v' d6 ekernel.pid_max = 316448
* Applying /etc/sysctl.d/k8s.conf ...
net.bridge.bridge-nf-call-ip6tables = 1
. n8 C' H/ f# T- y/ ?net.bridge.bridge-nf-call-iptables = 1
* Applying /etc/sysctl.conf ...
4 I7 N% _( g' z3 F5 `$ Lkernel.pid_max = 316448
% ]" ^  u% }5 N6 l$ d2 M1 c/ r6 k[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
[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
    [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"
time="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"
' p# B# x" {6 Y' v9 G# i, error: exit status 1
& O* e8 P% j9 ]% a' {    [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
7 r  @( s- L. r6 j! ^! Y7 ~9 v[root@kubernetes-master net]# docker ps

; w1 X! F5 b: v- Q' _* T, ~1 a4 OCannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
4 I; b+ ]* z. F  s[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
[root@kubernetes-master net]# systemctl enable docker.service
% `/ c) q5 U4 L& ]Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.
7 M& X, o) ]+ ~: W* f[root@kubernetes-master net]# systemctl status cri-docker.service
! A1 A9 \8 w/ |( k5 `* x● cri-docker.service - CRI Interface for Docker Application Container Engine
5 g/ V5 W8 F; y- t8 Y9 h  T   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
' Y7 p/ G$ \# G& _( O9 `1 L     Docs: https://docs.mirantis.com
; I6 L% S# I% i" \3 J Main PID: 2909 (code=exited, status=1/FAILURE)

Sep 15 10:46:49 kubernetes-master systemd[1]: Failed to start CRI Interface for Docker Application C...ne.
7 S2 i6 I6 F9 ~; \% J5 XSep 15 10:46:49 kubernetes-master systemd[1]: Unit cri-docker.service entered failed state.
+ j0 A9 y: a& y, o: D: X9 a" |& \Sep 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.
8 \$ i( ]' e. Q( HSep 15 10:46:51 kubernetes-master systemd[1]: Stopped CRI Interface for Docker Application Container...ne.
Sep 15 10:46:51 kubernetes-master systemd[1]: start request repeated too quickly for cri-docker.service
Sep 15 10:46:51 kubernetes-master systemd[1]: Failed to start CRI Interface for Docker Application C...ne.
8 v1 B% @% g. Z5 wSep 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.
( t0 Y7 B. i$ X/ p) a" ^1 z[root@kubernetes-master net]# systemctl restart cri-docker.service
[root@kubernetes-master net]# systemctl status cri-docker.service
( A  ^: C  S1 k● cri-docker.service - CRI Interface for Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/cri-docker.service; enabled; vendor preset: disabled)
1 G( z* q0 b( Y   Active: active (running) since Sun 2024-09-15 10:48:38 CST; 1s ago
     Docs: https://docs.mirantis.com
Main PID: 3339 (cri-dockerd)
8 Z  {$ k2 j% T7 \$ `4 b& s" D5 |    Tasks: 8
8 ?* a8 ]0 a3 O, m2 G% E, C+ O   Memory: 16.2M
! W) O9 X' E: a: c2 ?' l+ A   CGroup: /system.slice/cri-docker.service
           └─3339 /usr/bin/cri-dockerd --container-runtime-endpoint fd:// --pod-infra-container-image=r...
4 l+ g  e; D  u
7 M: ?8 ]! S& V- G$ 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"
: o* G3 `' ]  w6 HSep 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"
Sep 15 10:48:38 kubernetes-master cri-dockerd[3339]: time="2024-09-15T10:48:38+08:00" level=info msg...ive
- Q4 z0 ?! T4 {: F! t, ZSep 15 10:48:38 kubernetes-master cri-dockerd[3339]: time="2024-09-15T10:48:38+08:00" level=info msg...fs"
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...,}"
4 a4 B7 S% L+ G* k* CSep 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"
Hint: Some lines were ellipsized, use -l to show in full.

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  
: K! @& f& v' h4 I[init] Using Kubernetes version: v1.28.0
% }; ?* d; W& |9 n3 g% Q[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
* ?: l" T+ _( J4 O[preflight] This might take a minute or two, depending on the speed of your internet connection
3 }. F* |6 X- D5 Q  ~; `[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
$ U( [, n, F+ Z7 @; k

, o" }3 z: V( W9 Q* ~1 I! L也就是说docker未启动就会报错