Agent pod failed about kubectl-debug

[aylei]

(1) Failed to Pulling image "aylei/debug-agent:latest", how to fix it? Or What is the credential for pulling down image?

It might be your node did not have network access to dockerhub or it was rate-limited at that time, you can use kubectl describe po <pod-name> to find out the exact reason

How to fix PodFitsHostPorts?

Agent port claims a host port, so you can only run one agent-pod in a Node, and in your it is the one that suffering ImagePullBackoff

[barryzhounb]

Thanks @aylei

Now I fixed the above issues.
When I ran command "kubectl debug ecgateway-86d67cb79d-8vhnc", a new issue came up, any ideas for that? How to fix it.

Agent Pod info: [Name:debug-agent-pod-d0bebc4e-4d62-11eb-9f4f-dca904978b2f, Namespace:default, Image:aylei/debug-agent:latest, HostPort:10027, ContainerPort:10027]
Waiting for pod debug-agent-pod-d0bebc4e-4d62-11eb-9f4f-dca904978b2f to run...
pod ecgateway-86d67cb79d-8vhnc PodIP 10.254.16.200, agentPodIP 10.16.36.245
wait for forward port to debug agent ready...
Forwarding from 127.0.0.1:10027 -> 10027
Forwarding from [::1]:10027 -> 10027
Handling connection for 10027
                             Start deleting agent pod ecgateway-86d67cb79d-8vhnc 
end port-forward...
                   error execute remote, unable to upgrade connection: Failed to construct RuntimeManager.  Error- only docker and containerd container runtimes are suppored right now
error: unable to upgrade connection: Failed to construct RuntimeManager.  Error- only docker and containerd container runtimes are suppored right now

[aylei]

what's your container runtime?

[barryzhounb]

Sorry, I don't know what is "container runtime", so I could not answer you. Because I use default configurations, I wish it works, unfortunately it failed. Is there any configurations that I need to change in order to fix it? I am sorry for spending too much your time, I am not sure if it is possible to have a video chat in order to solve this issue such as Webex or Zoom, I live in Canada.