-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
国产麒麟ky10.aarch64上安装sealos,报错 #3187
Comments
[ERROR FileContent--proc-sys-net-ipv4-ip_forward]: /proc/sys/net/ipv4/ip_forward contents are not set to 1 |
------------------ 原始邮件 ------------------
发件人: "labring/sealos" ***@***.***>;
发送时间: 2023年5月31日(星期三) 晚上6:00
***@***.***>;
***@***.******@***.***>;
主题: Re: [labring/sealos] 国产麒麟ky10.aarch64上安装sealos,报错 (Issue #3187)
[ERROR FileContent--proc-sys-net-ipv4-ip_forward]: /proc/sys/net/ipv4/ip_forward contents are not set to 1
好像是内核不支持
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
问题已解决
|
请问您是如何解决此问题的? @fengxsong |
How did you solve this problem? @fengxsong |
升级了内核解决了?哪个版本的内核啊 |
Did you upgrade the kernel? Which version of the kernel? |
Sealos Version
sealos_4.2.1-rc3_linux_arm64_
How to reproduce the bug?
在如下麒麟v10服务器上
Linux node1 4.19.90-23.23.v2101.ky10.aarch64 #1 SMP Fri May 6 11:45:57 CST 2022 aarch64 aarch64 aarch64 GNU/Linux
在线安装执行
sealos run labring/kubernetes-docker:v1.24.14-4.2.0 labring/helm:v3.8.2 labring/calico:v3.24.1 --masters 192.168.1.123,192.168.1.124,192.168.1.125 -p passwd
执行后出现错误
What is the expected behavior?
2023-05-31T16:46:31 info start to copy etc pki files to masters
2023-05-31T16:46:31 info start to copy etc pki files to masters
2023-05-31T16:46:31 info start to create kubeconfig...
2023-05-31T16:46:32 info start to copy kubeconfig files to masters
2023-05-31T16:46:32 info start to copy static files to masters
2023-05-31T16:46:32 info start to init master0...
2023-05-31T16:46:32 info domain apiserver.cluster.local:192.168.1.74 append success
W0531 16:46:32.608848 1059435 initconfiguration.go:306] error unmarshaling configuration schema.GroupVersionKind{Group:"kubelet.config.k8s.io", Version:"v1beta1", Kind:"KubeletConfiguration"}: strict decoding error: unknown field "localStorageCapacityIsolation"
W0531 16:46:32.611197 1059435 configset.go:177] error unmarshaling configuration schema.GroupVersionKind{Group:"kubelet.config.k8s.io", Version:"v1beta1", Kind:"KubeletConfiguration"}: strict decoding error: unknown field "localStorageCapacityIsolation"
W0531 16:46:32.611752 1059435 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/var/run/cri-dockerd.sock". Please update your configuration!
W0531 16:46:32.611786 1059435 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: 127.0.0.1; the provided value is: 0.0.0.0
[init] Using Kubernetes version: v1.24.14
[preflight] Running pre-flight checks
[WARNING FileExisting-socat]: socat not found in system path
error execution phase preflight: [preflight] Some fatal errors occurred:
[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
2023-05-31T16:46:32 error Applied to cluster error: failed to init init master0 failed, error: exit status 1. Please clean and reinstall
Error: failed to init init master0 failed, error: exit status 1. Please clean and reinstall
[root@yl02 sealos]# sealos reset
2023-05-31T16:48:00 info are you sure to delete these nodes?
What do you see instead?
No response
Operating environment
Additional information
No response
The text was updated successfully, but these errors were encountered: