-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Server 2022 runner does not have IPv6 connectivity #9401
Comments
Duplicte of #668 |
Hi @mikhailkoliada, I hope you are doing well.
This issue was not answered. |
@jozefizso hey, we do not support ipv6 for both inbound or outbound ways, so it is expected |
@mikhailkoliada This is not expected for a networking technology which is 28 years old in a world where servers are accessible using IPv6. |
https://github.com/orgs/community/discussions/10539#discussioncomment-2063601 |
Description
GitHub hosted cloud runners with Windows Server are not able to communicate with IPv6 hosts.
IPv6 was introduced on December 1995, 28 years ago. We should be able to use it in workflows.
Platforms affected
Runner images affected
Image version and build link
Current runner version: '2.313.0'
Operating System
Microsoft Windows Server 2022
10.0.20348
Datacenter
Runner Image
Image: windows-2022
Version: 20240218.2.0
Included Software: https://github.com/actions/runner-images/blob/win22/20240218.2/images/windows/Windows2022-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F20240218.2
Is it regression?
no
Expected behavior
I can be able to connect to IPv6 hosts.
Actual behavior
Cloud runners are able to connect to IPv6 hosts.
Repro steps
Run this command on Windows Server runners:
The
curl
will fail with errorcurl: (6) Could not resolve host ifconfig.co
.The text was updated successfully, but these errors were encountered: