You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Historically, when containerd events were received, we created listeners to leverage the WSL listener forwarding feature. This was necessary because containerd, unlike Docker, didn't create listeners for running containers. Instead, it routed traffic through iptables rules in the CNI-HOSTPORT-DNAT chain, manipulating container traffic directly.
However, the WSL listener forwarding feature is no longer in use with the new namespaced network configuration. As a result, we no longer need to create listeners for each running container manually, and it should be removed.
The text was updated successfully, but these errors were encountered:
Historically, when containerd events were received, we created listeners to leverage the WSL listener forwarding feature. This was necessary because containerd, unlike Docker, didn't create listeners for running containers. Instead, it routed traffic through iptables rules in the CNI-HOSTPORT-DNAT chain, manipulating container traffic directly.
However, the WSL listener forwarding feature is no longer in use with the new namespaced network configuration. As a result, we no longer need to create listeners for each running container manually, and it should be removed.
The text was updated successfully, but these errors were encountered: