Lab 6.1. Failed to start busybox

Gim6626 · April 2021

I followed lab 6.1 guide till the end and got troubles running busybox:

$ kubectl run -i -t busybox --image=busybox --restart=Never
If you don't see a command prompt, try pressing enter.
Error attaching, falling back to logs: unable to upgrade connection: pod does not exist
Error from server (NotFound): the server could not find the requested resource ( pods/log busybox)

Could anybody help?

chrispokorni · April 2021

Hi @Gim6626,

It seems this is a recurring behavior in your cluster that pods cannot be found after they have been deployed. Are your nodes isolated by any firewalls, and can they access the outside world?

Regards,
-Chris

Gim6626 · April 2021

Hi @chrispokorni,

Should we continue here or in https://forum.linuxfoundation.org/discussion/858777/lab-4-2-could-not-get-pod-logs-error-from-server-notfound if you've said that it is related?

Anyway answering the question.

I haven't configured any firewalls, both (master and worker) nodes are fresh installed Ubuntu Server 18.04.5 as Virtual Box machines.

Both has two network cards - NAT and "Host-only Adapter" (both connected to same).

Both can access Internet (from first card) and each other (from second card).

Gim6626 · April 2021

Solved, see https://forum.linuxfoundation.org/discussion/comment/29437/#Comment_29437, it was network related

Lab 6.1. Failed to start busybox

Comments

Categories

Upcoming Training

Kubernetes Administration (LFS458)

Linux System Administration (LFS301)

Open Source Virtualization (LFS462)

Linux Kernel Debugging and Security (LFD440)