HA logs - repeated monitor_docker error No 'networks' found in raw packet

[kbarter]

I have a problem that looks like it might be similar to issue 10. The only difference is that I am getting the message for any docker containers that I have that are using a VPN container for their networking.

2020-11-21 10:10:48 ERROR (Thread-3) [custom_components.monitor_docker.helpers] App1: No 'networks' found in raw packet
2020-11-21 10:10:48 ERROR (Thread-3) [custom_components.monitor_docker.helpers] %s: Too many errors on 'networks' stats, disabling monitoring
2020-11-21 10:10:49 ERROR (Thread-3) [custom_components.monitor_docker.helpers] App2: Can not determine network usage for container ('networks')
2020-11-21 10:10:49 ERROR (Thread-3) [custom_components.monitor_docker.helpers] App2: No 'networks' found in raw packet
2020-11-21 10:10:49 ERROR (Thread-3) [custom_components.monitor_docker.helpers] %s: Too many errors on 'networks' stats, disabling monitoring
2020-11-21 10:10:49 ERROR (Thread-3) [custom_components.monitor_docker.helpers] App3: Can not determine network usage for container ('networks')
2020-11-21 10:10:49 ERROR (Thread-3) [custom_components.monitor_docker.helpers] App3: No 'networks' found in raw packet
2020-11-21 10:10:49 ERROR (Thread-3) [custom_components.monitor_docker.helpers] %s: Too many errors on 'networks' stats, disabling monitoring
2

Here is the relevant parts of my dockercompose.yaml

    network_mode: "service:vpn"

[ualex73]

I finally got my setup done, I should be able to test this one. I should have an update in a few days.

[valgeirhelgi]

I was having the same error. I checked portainer and the containers were no longer registered in their networks. Example wireguard was not registered to the nework "wireguard_default", after re-regestering them to the networks in portainer the error stopped.