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
We cannot use the latest github.com/inetaf/tcpproxy commit because of 61dc4e1 which causes a regression in podman containers/podman#23616
My feeling is that this revert is either hiding a gvisor-tap-sock bug which has been present for a long time, or it's avoiding a newly introduced bug in inetaf/tcpproxy. In either cases ,it would be good to understand better what caused the issue leading to the revert. The podman bug has a reproducer for it.
The text was updated successfully, but these errors were encountered:
We cannot use the latest github.com/inetaf/tcpproxy commit because of 61dc4e1 which causes a regression in podman containers/podman#23616
My feeling is that this revert is either hiding a gvisor-tap-sock bug which has been present for a long time, or it's avoiding a newly introduced bug in inetaf/tcpproxy. In either cases ,it would be good to understand better what caused the issue leading to the revert. The podman bug has a reproducer for it.
The text was updated successfully, but these errors were encountered: