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

1320503165

3 {) D* [5 I0 h% Q! |3 ]
! I; c8 w( d8 v   [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

5 I- Y' \' B# s


1 }  \8 T  t: C[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
! x+ d9 u' a8 X* 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
2 a9 Z, j- l1 p* Applying /usr/lib/sysctl.d/10-default-yama-scope.conf ...
kernel.yama.ptrace_scope = 0
* Applying /usr/lib/sysctl.d/50-default.conf ...
8 H/ P2 ?  g* g/ z' x+ V5 G) q( F, g) i$ Qkernel.sysrq = 16
kernel.core_uses_pid = 1
kernel.kptr_restrict = 1
net.ipv4.conf.default.rp_filter = 1
5 t2 b) g" ~' znet.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
$ o8 _( ^! f8 o  I! ]+ V+ P3 y- Tnet.ipv4.conf.all.promote_secondaries = 1
9 D# s4 b! u+ j' pfs.protected_hardlinks = 1
/ J/ Z' @. ]' c: z! ^) b, Gfs.protected_symlinks = 1
* Applying /etc/sysctl.d/99-sysctl.conf ...
kernel.pid_max = 316448
* V- k6 G7 B2 b8 @/ H" r* Applying /etc/sysctl.d/k8s.conf ...
net.bridge.bridge-nf-call-ip6tables = 1
/ ~6 ]/ d/ y; p- _5 t3 T2 H  }net.bridge.bridge-nf-call-iptables = 1
% K6 _& B/ m/ y9 }) A0 q* Applying /etc/sysctl.conf ...
# D8 e. _/ C% f- l3 wkernel.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  
* p$ e2 X1 c( |3 U/ ]5 V  b[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"
) Z1 _/ V8 T  U) ?/ K, error: exit status 1
( @$ I& {& Y  L( z) e, k" f    [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=...`
( h' w8 G) l, f. G( |0 JTo see the stack trace of this error execute with --v=5 or higher
6 t( `/ I6 ^, ~[root@kubernetes-master net]# docker ps

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
! S& W8 x" U+ {* m[root@kubernetes-master net]#
: I9 O! K  O! @- b5 ~1 k[root@kubernetes-master net]# systemctl restart docker.service
5 Z7 N2 [. F6 @. j2 [[root@kubernetes-master net]# docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
( }4 w3 W1 E# w0 R[root@kubernetes-master net]# systemctl enable docker.service
7 H& P) h' G/ V& e& L* [. VCreated 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
$ W) A& ]% H) p● cri-docker.service - CRI Interface for Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/cri-docker.service; enabled; vendor preset: disabled)
8 {$ Y! V& x. r0 \% i% i   Active: failed (Result: start-limit) since Sun 2024-09-15 10:46:51 CST; 1min 37s ago
2 x  s. ~2 b- {5 }$ g( \/ M+ g     Docs: https://docs.mirantis.com
Main PID: 2909 (code=exited, status=1/FAILURE)

, |2 p- s: ~4 z3 L( m5 @6 M( cSep 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.
Sep 15 10:46:49 kubernetes-master systemd[1]: cri-docker.service failed.
1 k; T( G) B: N+ f& N7 C. R( jSep 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.
6 o. d4 c6 P/ X6 {# n/ e: ~Sep 15 10:46:51 kubernetes-master systemd[1]: start request repeated too quickly for cri-docker.service
+ w7 ]  O1 \, c; O( T; qSep 15 10:46:51 kubernetes-master systemd[1]: Failed to start CRI Interface for Docker Application C...ne.
. u. B9 p, h' k1 S+ Q* tSep 15 10:46:51 kubernetes-master systemd[1]: Unit cri-docker.service entered failed state.
5 V) T9 u" G6 ~; {% p) K; g. mSep 15 10:46:51 kubernetes-master systemd[1]: cri-docker.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[root@kubernetes-master net]# systemctl restart cri-docker.service
7 {4 J$ G$ h  d, e: r. K4 H9 {. W[root@kubernetes-master net]# systemctl status cri-docker.service
● cri-docker.service - CRI Interface for Docker Application Container Engine
7 I) q! C9 b' C; ^# X  J7 S   Loaded: loaded (/usr/lib/systemd/system/cri-docker.service; enabled; vendor preset: disabled)
3 u0 q$ B- e# O1 y3 T* n: B  Y   Active: active (running) since Sun 2024-09-15 10:48:38 CST; 1s ago
& @; O; S- d# B6 w* |     Docs: https://docs.mirantis.com
Main PID: 3339 (cri-dockerd)
    Tasks: 8
   Memory: 16.2M
   CGroup: /system.slice/cri-docker.service
  X- A5 d$ N' G' D: D+ b           └─3339 /usr/bin/cri-dockerd --container-runtime-endpoint fd:// --pod-infra-container-image=r...
* n- B% t# E8 p: h3 q
Sep 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"
# U$ ?; v* b0 O6 Y9 n2 R; E% a& P5 G& _Sep 15 10:48:38 kubernetes-master cri-dockerd[3339]: time="2024-09-15T10:48:38+08:00" level=info msg...ive
( i' `" a8 F0 B0 w. n1 {5 v: 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.
0 b8 ]1 b* y1 I3 ]- W& i; ESep 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"
* c3 b$ l# X- M6 eHint: Some lines were ellipsized, use -l to show in full.
. x- U2 Q" a6 q( W

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  
$ u1 e0 ~  d. m( v- f" F[init] Using Kubernetes version: v1.28.0
[preflight] Running pre-flight checks
2 ]$ J$ M( l) `* e0 M% \[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
( j3 _7 A( R9 K" t/ [) g+ Z& ~. g[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'

" [7 S% ~2 u9 S7 ?1 H
也就是说docker未启动就会报错