ksniff VS netshoot

so probably the right way is to use some tool like that (ksniff) or setup a sidecar container. But I am still curious to why I get the above error.

I've used https://github.com/eldadru/ksniff with success. Recently on this sub Kubeshark was also mentioned.

Link to GitHub Repository

There also is https://github.com/eldadru/ksniff which starts wireshart GUI

I have used Ksniff as a kubectl plugin that act as a "Wireshark tool" for containers https://github.com/eldadru/ksniff

I've found ksniff useful for monitoring Kubernetes traffic with wireshark: https://github.com/eldadru/ksniff

KSniff https://github.com/eldadru/ksniff lets you do full packet capture.

ksniff - known as sniff is a tool for debugging and capturing networking data. It's able to attach to a pod and using tcpdump to forward networking data to your local Wireshark. This tool also works pretty well with tshark - the command-line version of Wireshark.

Install ksniff - https://github.com/eldadru/ksniff#installation

Now, let's use netshoot, a Docker image equipped with a set of networking troubleshooting tools that can be used for Docker networking.

nicolaka/netshoot for sure. having a preloaded array of networking troubleshooting tools in an image for kubernetes debugging is a godsend.

First off, it seems like getting tcpdump or Wireshark to capture from the container network and dumping to a file will take some extra steps. (A lot of blog posts seem to recommend this Github project - https://github.com/nicolaka/netshoot)

Some hints how to debug such problems in the future: 1. ufw drops/rejections are logged (use dmesg to view them) 2. wireshark shows all connection attempts, even those that are blocked by firewall 3. ss or netstat shows if the server is actually listening for connections 4. netshoot allows to enter docker container network namespace and do pings, curl or telnet from there