We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What happened:
use docker(kindest/node:v1.21.1) start by kind as edge node to join a superEdge k8s cluster run: ./edgeadm join ...
./edgeadm join ...
get the error: E1117 14:39:31.802393 3427 init_node.go:47] Run init node shell: /tmp/edgeadm/edge-install/script/init-node.sh, error: exit status 126
E1117 14:39:31.802393 3427 init_node.go:47] Run init node shell: /tmp/edgeadm/edge-install/script/init-node.sh, error: exit status 126
add set -x to init-node.sh, rerun the script and get the output:
set -x
++ modprobe -- nf_conntrack_ipv4 modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.10.47-linuxkit
modprobe -- nf_conntrack_ipv4
The reason:
after some dig, and found out nf_conntrack_ipv4 is updated to nf_conntrack since the kernel 4.19 and only kube-proxy v1.13 is strong required this
nf_conntrack_ipv4
nf_conntrack
and superEdge supported kube-proxy is higher than v1.13 (v1.18.2?) so, can we remove this?
How to reproduce it (as minimally and precisely as possible):
./edgeadm join
The text was updated successfully, but these errors were encountered:
by the way
when exec ./edgeadm join ... -v 6 got :
./edgeadm join ... -v 6
stderr: /bin/bash: line 1: /tmp/edgeadm/edge-install/script/init-node.sh: Permission denied
check the permission:
ls -alh /tmp/edgeadm/edge-install/script/init-node.sh -rwxr-xr-x 1 root root 2.9K Nov 17 15:10 /tmp/edgeadm/edge-install/script/init-node.sh
run findmnt command, and got a nonexec as expected.
findmnt
nonexec
findmnt --target /tmp/edgeadm/edge-install/script/init-node.sh TARGET SOURCE FSTYPE OPTIONS /tmp tmpfs tmpfs rw,nosuid,nodev,noexec,relatime
so have to remount
mount -o remount,rw,nosuid,nodev,exec,relatime /tmp
I don't know why kind does nonexec to /tmp dir. But it may be under consideration when superEdge start to support kind.
Sorry, something went wrong.
init-node.sh is a custom script, if some scripts are not suitable for your needs, you can customize You can refer to: https://github.com/superedge/superedge/blob/main/docs/installation/install_edge_kubernetes.md#3-custom-node-initialization-script @caniszczyk adamzhoul
thanks
No branches or pull requests
What happened:
use docker(kindest/node:v1.21.1) start by kind as edge node to join a superEdge k8s cluster
run:
./edgeadm join ...
get the error:
E1117 14:39:31.802393 3427 init_node.go:47] Run init node shell: /tmp/edgeadm/edge-install/script/init-node.sh, error: exit status 126
add
set -x
to init-node.sh, rerun the script and get the output:modprobe -- nf_conntrack_ipv4
The reason:
after some dig, and found out
nf_conntrack_ipv4
is updated tonf_conntrack
since the kernel 4.19and only kube-proxy v1.13 is strong required this
and superEdge supported kube-proxy is higher than v1.13 (v1.18.2?)
so, can we remove this?
How to reproduce it (as minimally and precisely as possible):
./edgeadm join
The text was updated successfully, but these errors were encountered: