Reopen Issue 6336

[snwfdhmp]

The issue #6336 has not been reopened yet despite being critical and security related and despite having lots of developers reporting this bug.

Please take a moment to acknowledge this bug and try to fix it.

If you don't consider this important enough to fix, please announce it on the issue so we don't expect any improvement on this topic.

Thank you.

[rolpaul]

I agree that this is a critical issue. ssh is important in professional company networks.
I can still reproduce this problem still exists on docker-compose 1.25.0 linux (ubuntu)
I can not confirm the statement in #6338 that this was fixed and merged in #6388.
As @sampwing points out please acknowledge this bug and tell us how to proceeed, either here in #7709 or in reopened #6336.

[konzinov]

For those who facing the same issue:

After digging into paramiko i figured out it tries to establish ssh connection throught many network interfaces using ipv6 option first.

This can lead to some timeout Error (it's the same error that appears) due to network configurations or ssh over ipv6 configurations on the target host (See AddressFamily option for SSH).

To fix it i just disabled ipv6 on my computer.
it can be done on mac with networksetup -setv6off Ethernet && networksetup -setv6off Wi-Fi

But if you definitely want to use ipv6 make sure you can ssh using ipv6 and it should work with paramiko too.

refers to #6336

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because it had not recent activity during the stale period.