On Wed, Nov 18, 2020 at 1:27 PM Joakim Roubert <[email protected]> wrote:
> On 2020-11-17 20:39, Bruce Ashfield wrote: > > > > root@qemux86-64:~# kubectl get pods -n kube-system > > NAME READY STATUS RESTARTS AGE > > local-path-provisioner-7ff9579c6-bd947 0/1 CrashLoopBackOff 822m > > coredns-66c464876b-76bdl 0/1 CrashLoopBackOff 822m > > helm-install-traefik-mvt5k 0/1 CrashLoopBackOff 822m > > metrics-server-7b4f8b595-ck5kz 0/1 CrashLoopBackOff 822m > > root@qemux86-64:~# > > From my own experience with CrashLoopBackOff situations is that there > may be serveral different things causing that. Can you trace down what > is causing the CrashLoopBackOff here? > Not really. The build seems to have some sort of misconfiguration and no logs are created (and hence can't be accessed via kubectl). Running the server on the command line just gets us reams of messages and a lot of false leads (too many nameservers, iptables --random-fully not supported, etc ). I've tried a few variants today, but can't get any really simple logs out. I'll do more tomorrow. I've been able to confirm that my packagegroup/image type runs docker, containerd, and runc launched containers just fine, so this is just some quirk/idiocy of k*s that is causing the problem. Bruce > > BR, > > /Joakim > > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#6104): https://lists.yoctoproject.org/g/meta-virtualization/message/6104 Mute This Topic: https://lists.yoctoproject.org/mt/78314751/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
