Hi dudes!
I tried to run kubectl debug and attach an ephemeral container to an already running pod with your image wbitt/network-multitool, but it gave me no output and I can't see any processes from this container :(
How I run it:
kubectl debug -it --image=wbitt/network-multitool POD_NAME --target CONTAINER_NAME
What I see:
Targeting container "MY_AWESOME_CONTAINER". If you don't see processes from this container it may be because the container runtime doesn't support this feature.
Defaulting debug container name to debugger-tlzvl.
If you don't see a command prompt, try pressing enter.
pwd
ls
who
cd
^CSession ended, the ephemeral container will not be restarted but may be reattached using 'kubectl attach MY_AWESOME_POD -c debugger-tlzvl -i -t' if it is still running
I tried to run several commands (pwd, ls, etc...)
But when I run busybox, it gave me output and interactive session:
kubectl debug -it --image=busybox POD_NAME --target CONTAINER_NAME
Targeting container "CONTAINER_NAME". If you don't see processes from this container it may be because the container runtime doesn't support this feature.
Defaulting debug container name to debugger-6nrms.
If you don't see a command prompt, try pressing enter.
/ #
/ #
/ #
/ # pwd
/
/ # ls
bin dev etc home lib lib64 proc root run sys tmp usr var
/ #
cri and k8s versions here:
crio version 1.28.8
Version: 1.28.8
GitCommit: unknown
GitCommitDate: unknown
GitTreeState: clean
BuildDate: 2024-07-05T13:42:21Z
GoVersion: go1.21.11
Compiler: gc
Platform: linux/amd64
Linkmode: dynamic
BuildTags:
containers_image_ostree_stub
libdm_no_deferred_remove
containers_image_openpgp
seccomp
selinux
LDFlags: unknown
SeccompEnabled: true
AppArmorEnabled: false
kubectl version
Client Version: v1.28.12
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.8
Hi dudes!
I tried to run
kubectl debugand attach an ephemeral container to an already running pod with your imagewbitt/network-multitool, but it gave me no output and I can't see any processes from this container :(How I run it:
kubectl debug -it --image=wbitt/network-multitool POD_NAME --target CONTAINER_NAMEWhat I see:
I tried to run several commands (pwd, ls, etc...)
But when I run busybox, it gave me output and interactive session:
cri and k8s versions here: