You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some test scripts I sometimes use ksniff to sniff a container and save to output to a capture file by use the "-o" flag to ksniff, for example:
kubectl sniff -c -o
I also tried to use the "-p" flag for priviledge mode that starts a new pod.
But when I try to stop/quit the ksniff, either by "ctrl-c" or let my script kill the ksniff process, then the "ksniff"-pod is kept aswell as the "static-tcpdump" process in the container (if I launch without the "-p" flag).
If I do not use the "-o" flag, and insteasd let it launch Wireshark, then everything seem to be safely stoped and clean up after quit the Wireshark application. But if I use the "-o" option and send the stream to a file, I have not yeat found a nice way to stop/quit the ksniff application.
The text was updated successfully, but these errors were encountered:
In some test scripts I sometimes use ksniff to sniff a container and save to output to a capture file by use the "-o" flag to ksniff, for example:
kubectl sniff -c -o
I also tried to use the "-p" flag for priviledge mode that starts a new pod.
But when I try to stop/quit the ksniff, either by "ctrl-c" or let my script kill the ksniff process, then the "ksniff"-pod is kept aswell as the "static-tcpdump" process in the container (if I launch without the "-p" flag).
If I do not use the "-o" flag, and insteasd let it launch Wireshark, then everything seem to be safely stoped and clean up after quit the Wireshark application. But if I use the "-o" option and send the stream to a file, I have not yeat found a nice way to stop/quit the ksniff application.
The text was updated successfully, but these errors were encountered: