v2.1.16 fixes missing Docker/containerd information in some situations #25
Closed
thediveo
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In some situations albeit Edgeshark correctly detected the presence of the Docker (and containerd) container engine, it would not connect to the API endpoint(s). The result was a subtle degradation in that while the network topology was still displayed, yet Docker container and network names were missing. Restarting Edgeshark did not remedy the situation.
This bug is now fixed in v2.1.16, so we ask all Edgeshark users to update even if you weren't affected by this bug in the past.
Ironically, the bug was about multiple whitespace in a particular Linux kernel pseudo file in right-aligned text columns.
Beta Was this translation helpful? Give feedback.
All reactions