After the announcement that the Kubic project is in a wind-down process, I shifted my interest to MicroOS. I installed from an ISO image and did a transactional-update and rebootet. Next step was to install k3s using transactional-update pkg in k3s which installed k3s. When starting k3s server, either manually or via systemctl, however, k3s segfaults: ... INFO[0000] To join node to cluster: k3s agent -s https://172.16.18.142:6443 -t ${NODE_TOKEN} panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x562c36fa6d1c] goroutine 1 [running]: reflect.mapiternext(0xc0002348d0?) /usr/lib64/go/1.18/src/runtime/map.go:1378 +0x19 github.com/modern-go/reflect2.(*UnsafeMapIterator).UnsafeNext(0x9?) ... (The actual error message is a lot longer). What am I missing or doing wrong here? - Marc
Am 28.05.2022 um 12:35 schrieb Marc Balmer
: After the announcement that the Kubic project is in a wind-down process, I shifted my interest to MicroOS.
I installed from an ISO image and did a transactional-update and rebootet.
Next step was to install k3s using transactional-update pkg in k3s which installed k3s.
When starting k3s server, either manually or via systemctl, however, k3s segfaults:
... INFO[0000] To join node to cluster: k3s agent -s https://172.16.18.142:6443 -t ${NODE_TOKEN} panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x562c36fa6d1c]
goroutine 1 [running]: reflect.mapiternext(0xc0002348d0?) /usr/lib64/go/1.18/src/runtime/map.go:1378 +0x19 github.com/modern-go/reflect2.(*UnsafeMapIterator).UnsafeNext(0x9?) ...
(The actual error message is a lot longer).
What am I missing or doing wrong here?
FWIW, this installs k3s 1.22.3 with k3s in /usr/bin. When I install k3s directly from get.k3s.io http://get.k3s.io/ using the curl method described on their website, I get a newer version 1.23.x which installs into /usr/local/bin and which works. I would prefer the transactional-update route, though...
------- Original Message -------
On Saturday, May 28th, 2022 at 7:29 PM, Marc Balmer
FWIW, this installs k3s 1.22.3 with k3s in /usr/bin. When I install k3s directly from get.k3s.io using the curl method described on their website, I get a newer version 1.23.x which installs into /usr/local/bin and which works. I would prefer the transactional-update route, though...
I have little to no experience with k3s from the repos, but after a quick test I got the same error you did. Might be better to open a bug report on it? With that said in my combustion scripts I also use the upstream version instead of the rpm package: https://code.opensuse.org/adathor/combustion-dotconf/blob/main/f/K3s%20clust... -- Br, A.
Am 28.05.2022 um 14:41 schrieb Attila Pinter
: ------- Original Message ------- On Saturday, May 28th, 2022 at 7:29 PM, Marc Balmer
wrote: FWIW, this installs k3s 1.22.3 with k3s in /usr/bin. When I install k3s directly from get.k3s.io using the curl method described on their website, I get a newer version 1.23.x which installs into /usr/local/bin and which works. I would prefer the transactional-update route, though...
I have little to no experience with k3s from the repos, but after a quick test I got the same error you did. Might be better to open a bug report on it?
With that said in my combustion scripts I also use the upstream version instead of the rpm package: https://code.opensuse.org/adathor/combustion-dotconf/blob/main/f/K3s%20clust...
How do you update the upstream version? Re-run the curl command? Or is there anything else needed? If understand things correctly, I can not revert to an older version of k3s if neded by rolling back to an older snapper snapshot, right? - Marc
participants (2)
-
Attila Pinter
-
Marc Balmer