@Apsu noted yesterday that this appears to relate to veth's staying behind after container restarts and that it's present in both AIO's and multi-node deployments. While this doesn't appear to affect the environment in a critical way, it may cause packet loss - this is yet to be confirmed. The workaround for now is to clean up leftover veth's in the environment using this script: https://gist.github.com/Apsu/7947a3347fcc86bb45a7
@Apsu noted yesterday that this appears to relate to veth's staying behind after container restarts and that it's present in both AIO's and multi-node deployments. While this doesn't appear to affect the environment in a critical way, it may cause packet loss - this is yet to be confirmed. The workaround for now is to clean up leftover veth's in the environment using this script: https:/ /gist.github. com/Apsu/ 7947a3347fcc86b b45a7