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

1320503165

7 Y2 T" U2 T2 {# Q" L
   [ERROR FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables does not exist
; t8 c) U5 `7 E2 ?  S# L6 h    [ERROR FileContent--proc-sys-net-ipv4-ip_forward]: /proc/sys/net/ipv4/ip_forward contents are not set to 1
: h# I. l9 c6 J+ v$ J

9 W5 {" T1 `0 M  u0 k, Z
+ Q) U  i/ C/ ]
' |2 d/ p$ K2 d. [& j0 u[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
% V* B/ {- o" F7 Q0 c2 m# @net.bridge.bridge-nf-call-iptables = 0
+ X: t. q. ^# ?' k. \1 Knet.bridge.bridge-nf-call-arptables = 0
; D9 U/ w4 t/ t, \* Applying /usr/lib/sysctl.d/10-default-yama-scope.conf ...
$ l, V$ m0 ?$ X/ U- Vkernel.yama.ptrace_scope = 0
4 p7 n2 n! g0 d/ I% y* Applying /usr/lib/sysctl.d/50-default.conf ...
. U4 i7 c- I: B7 F8 ?0 Ukernel.sysrq = 16
  L0 H7 N( p( I3 {' Nkernel.core_uses_pid = 1
kernel.kptr_restrict = 1
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
; s7 v- ]  J9 y8 q0 S* I0 l$ Nnet.ipv4.conf.all.accept_source_route = 0
$ t) Z% G& [; o/ {, g! w! Q0 o0 ^1 ?9 Enet.ipv4.conf.default.promote_secondaries = 1
1 y% A/ ^2 R7 Unet.ipv4.conf.all.promote_secondaries = 1
( a4 U9 P8 W  dfs.protected_hardlinks = 1
# ^* G( R1 A; k0 \fs.protected_symlinks = 1
* Applying /etc/sysctl.d/99-sysctl.conf ...
, k" A2 U5 t! w/ t% kkernel.pid_max = 316448
7 f1 d- f/ y, D1 K! e. a, k" K* Applying /etc/sysctl.d/k8s.conf ...
8 q# e) {# }! enet.bridge.bridge-nf-call-ip6tables = 1
7 M$ Z7 L% K" n( c( M6 F% ~net.bridge.bridge-nf-call-iptables = 1
6 S9 G, d# F0 d# i9 `' r, g* Applying /etc/sysctl.conf ...
4 k' W/ Y' L8 w! _( qkernel.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
& a7 s' k# f) S6 _9 H0 _/ \# b[preflight] Running pre-flight checks
  A8 g0 p* a6 b+ i) p, l) Cerror 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"
" w% l( y% R3 wtime="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"
9 G  R5 f4 _: d" B8 ?* P$ T, error: exit status 1
    [ERROR FileContent--proc-sys-net-ipv4-ip_forward]: /proc/sys/net/ipv4/ip_forward contents are not set to 1
- N3 f0 v$ j" C[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
4 \+ B& k- F. ^9 X" PTo see the stack trace of this error execute with --v=5 or higher
" }5 u; }' P4 y" [. Q[root@kubernetes-master net]# docker ps
& ]( l) }7 D, n  ^; `$ S- P9 o
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
" _. {2 g3 Q+ F: Q/ @[root@kubernetes-master net]#
[root@kubernetes-master net]# systemctl restart docker.service
" o# g4 ?. I% K$ }& H$ I[root@kubernetes-master net]# docker ps
4 ~9 F( i5 @9 R% s9 \, i* ]/ yCONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
( c  R* {( G  Q" ?  g# K0 E5 ^- `[root@kubernetes-master net]# systemctl enable docker.service
2 F5 f% t3 h' g. C; tCreated 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
● cri-docker.service - CRI Interface for Docker Application Container Engine
% S8 L% Y; v9 u4 H) r; Y   Loaded: loaded (/usr/lib/systemd/system/cri-docker.service; enabled; vendor preset: disabled)
$ c, h. J0 T- l/ Q   Active: failed (Result: start-limit) since Sun 2024-09-15 10:46:51 CST; 1min 37s ago
; Z, I8 P* f- }0 R* o% `/ r     Docs: https://docs.mirantis.com
Main PID: 2909 (code=exited, status=1/FAILURE)
& a/ \$ s* k! u' Z( W/ b) ^' M% J/ y8 n$ d
Sep 15 10:46:49 kubernetes-master systemd[1]: Failed to start CRI Interface for Docker Application C...ne.
. W9 d2 P6 Q$ bSep 15 10:46:49 kubernetes-master systemd[1]: Unit cri-docker.service entered failed state.
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.
Sep 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
* K7 ^) A) F' k! X& eSep 15 10:46:51 kubernetes-master systemd[1]: Failed to start CRI Interface for Docker Application C...ne.
' p$ d& Q8 b, C# lSep 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.
0 \$ `+ j% Y4 |' e7 M* C[root@kubernetes-master net]# systemctl restart cri-docker.service
[root@kubernetes-master net]# systemctl status cri-docker.service
5 f% C  D" [  u8 Z( 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  [! P0 l& K9 l& B8 a   Active: active (running) since Sun 2024-09-15 10:48:38 CST; 1s ago
$ D$ l6 @! G* ^2 U" ?3 F+ _     Docs: https://docs.mirantis.com
( q7 e0 u/ |( _) W. Q( [ Main PID: 3339 (cri-dockerd)
    Tasks: 8
   Memory: 16.2M
% Z8 H1 `: s. H6 L7 d   CGroup: /system.slice/cri-docker.service
$ S7 o6 Z- Q7 m$ e& Z9 |           └─3339 /usr/bin/cri-dockerd --container-runtime-endpoint fd:// --pod-infra-container-image=r...
2 K2 P1 A  |, v7 i, ]
- Q6 W8 q- f# v* [& ~Sep 15 10:48:38 kubernetes-master cri-dockerd[3339]: time="2024-09-15T10:48:38+08:00" level=info msg...0s"
  L1 k6 v  p) `8 ASep 15 10:48:38 kubernetes-master cri-dockerd[3339]: time="2024-09-15T10:48:38+08:00" level=info msg...ne"
7 d+ @7 H- Y2 H2 V4 w" g4 gSep 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"
3 i+ ~0 K; F* s! U! V$ kSep 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"
; a& c- C2 U* T0 p) _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...,}"
' w# e. T9 o/ c# j  k9 Y- k% N' ESep 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.

. i1 W) u8 B& S' T6 L+ u' f, M

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  
[init] Using Kubernetes version: v1.28.0
8 j7 B5 H( B; p8 b% i/ y% [9 y: l[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
' F; B* M& @; l3 K# B[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'
. W  ^& J" {% T2 T6 \" G& Q% z
) l9 W7 j! b7 O) o
- I/ C: b6 |6 C6 \也就是说docker未启动就会报错