No "/bin/timeout" binary in the trace container about kubectl-trace HOT 9 CLOSED

This must be that the tag latest isn't updated, it was last updated 2 months so it is missing this binary. This must still be the alpine image, which wouldn't have this binary.

@leogr @lainra can you please try specifying:

--imagename quay.io/iovisor/kubectl-trace-bpftrace:HEAD

And confirm that works?

@leodido @fntlnz we should either update that tag right away (i don't have access to quay.io i don't think, unless it's controlled by github access), or else release a binary that uses the right tag reference.

from kubectl-trace.

@leogr @lainra the quay.io/iovisor/kubectl-trace-bpftrace:latest tag has been updated, can you please confirm this problem is resolved without needing the --imagename flag?

from kubectl-trace.

@dalehamel could you please take a look at it? :)

from kubectl-trace.

I've the same issue too:

Warning  Failed     37s   kubelet, kind-control-plane  Error: failed to create containerd task: OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"/bin/timeout\": stat /bin/timeout: no such file or directory": unknown

I've tested with the latest installed from source.

from kubectl-trace.

@dalehamel yes, it works!

from kubectl-trace.

Sorry about this, the version I QA'd internally had this overridden. We'll get the tag fixed and then there shouldn't be any need to updated the kubectl-trace binary, it should just work.

from kubectl-trace.

Hi @dalehamel ,
now yes it works perfectly without --imagename

Image:         quay.io/iovisor/kubectl-trace-bpftrace:latest
Image ID:      sha256:df8ffc4e9f045fa3d8e066d939a8a6b26b5a19c6e68fb76ce64d354b63037a57

😊
Thank you!

from kubectl-trace.

thanks for confirming @leogr ! I'll close

from kubectl-trace.

@dalehamel
I also confirmed it works! Thank you for the quick fix!!!

from kubectl-trace.