k3s-io / k3s-root Goto Github PK
View Code? Open in Web Editor NEWK3s agent user space binaries
License: Apache License 2.0
K3s agent user space binaries
License: Apache License 2.0
What is the preferred way of including k3s-root in Buildroot built Linux image? I imagine building the k3s-root separately and adding the produced binaries using BR2_ROOTFS_OVERLAY
is one option. Is there a better way?
I just took binaries from https://github.com/k3s-io/k3s-root/releases/download/v0.10.0-rc.0/k3s-root-xtables-s390x.tar https://github.com/k3s-io/k3s-root/releases/download/v0.10.0-rc.0/k3s-root-s390x.tar and executed on s390x VM with SLE15-SP2:
./bin/aux/ebtables-legacy
Segmentation fault (core dumped)
kernel info:
sles@rancher-sles15sp2-jeos-ext4-devnet:~/k3s-root-release/k3s-root> uname -a
Linux rancher-sles15sp2-jeos-ext4-devnet 5.3.18-24.43-default #1 SMP Thu Dec 3 21:53:21 UTC 2020 (b48bf35) s390x s390x s390x GNU/Linux
just help:
strace ./bin/aux/ebtables-legacy --help
execve("./bin/aux/ebtables-legacy", ["./bin/aux/ebtables-legacy", "--help"], 0x3ffc307f3f8 /* 49 vars */) = 0
set_tid_address(0x10187d0) = 29685
brk(NULL) = 0x2fef000
brk(0x2ff1000) = 0x2ff1000
mmap(0x2fef000, 4096, PROT_NONE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x2fef000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3ff948fd000
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)
and list tables:
strace -f ./ebtables-legacy -L
execve("./ebtables-legacy", ["./ebtables-legacy", "-L"], 0x3ffe7cfe910 /* 45 vars */) = 0
set_tid_address(0x10187d0) = 29793
brk(NULL) = 0x2fba000
brk(0x2fbc000) = 0x2fbc000
mmap(0x2fba000, 4096, PROT_NONE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x2fba000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3ff9befd000
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)
socat was removed from containerd some time ago containerd/cri#1470 and this change was merged into the k3s containerd fork k3s-io/containerd@11a78d9
As far as I know we were just using socat for that. If that is the case we can remove it https://github.com/k3s-io/k3s-root/blob/master/buildroot/config#L3563
We are working on building k3s-root on s390x, since we need the binaries generated in k3s-root in order to build rke2 on s390x. Unfortunately, buildroot doesn't support static builds on s390x https://bugs.busybox.net/show_bug.cgi?id=14256
Would it be possible to use shared libraries instead of static?
It would be cool if k3s supported crun https://github.com/containers/crun
My understanding is that the license declaration is just for the k3s-root specific part, not for the embedded components like busybox. we could be more careful and specify GPLv2?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.