



Omitting the pipe works, so I can be fairly confident that everything is being passed around intact: # docker exec -it tcpdump-tcpdump-1 tcpdump -s 0 -Un -i eth0 -c 1 Tcpdump: listening on en0, link-type EN10MB (Ethernet), snapshot length 524288 bytes Removing Wireshark from the equation, piping it directly to tcpdump doesn't decode the packet like I'm expecting it to either: # tcpdump -s 0 -Un -i en0 -c 1 -w - | tcpdump -r. Replace uses of missing font family ".AppleSystemUIFont" with one that exists to avoid this cost. This kicks back pretty much as soon as it starts, with the Frame 1 too long error: # docker exec -it tcpdump-tcpdump-1 tcpdump -s 0 -Un -i eth0 -w - | wireshark -k -i. I've attached a tcpdump sidecar to one of my containers and I'm trying feed the capture into a local instance of Wireshark on macOS.
