mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #2482] Request to Disable IPv6 in Ubuntu Images to Enable JDK Installations #1146
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#1146
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @xingzhang-pku on GitHub (Oct 10, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2482
Act version
act version 0.0.0-SNAPSHOT-a30d171
Feature description
Issue Description
We are encountering an issue where our continuous integration (CI) process fails during JDK installation via IPv6 connections. Specifically, attempts to access the JDK bundles from Azul's API through IPv6 consistently fail, while IPv4 connections are successful.
Affected Images
The issue affects the following Docker images used in our GitHub Actions workflows:
catthehacker/ubuntu:act-latest-20240822catthehacker/ubuntu:act-22.04-20240822catthehacker/ubuntu:act-20.04-20240822Expected Behavior
We propose to disable IPv6 in the aforementioned Docker images to ensure reliable access to necessary external resources like JDK downloads during CI processes. This change would help not only our workflows but also other users who might face similar networking issues.
Steps to Reproduce
https://api.azul.com/zulu/download/community/v1.0/bundles/?os=linux&ext=tar.gz&bundle_type=jdk&javafx=false&arch=x86&hw_bitness=64Additional Information
Disabling IPv6 would be a temporary solution until a more robust handling of IPv4 and IPv6 compatibility issues can be implemented. This adjustment would facilitate a smoother development and testing process for teams relying on these Docker images.
Thank you for considering this enhancement to support better CI configuration and stability.
@xingzhang-pku commented on GitHub (Oct 10, 2024):
@ChristopherHX Could you please review the above issue? Your assistance would be greatly appreciated. Thank you!
@sebastien-perpignane commented on GitHub (Oct 11, 2024):
Hi,
How do you know it is related to IP v6 ? What kind of error do you get ?
Are you using setup-java to install the azul jdk ? or wget ? some other command ?
@xingzhang-pku commented on GitHub (Oct 12, 2024):
Thanks for your reply. I give the more detailed information below.
act command
act -j 'build_and_test' --rm -s GITHUB_TOKEN --use-new-action-cache --tool-cache-volume act-cache-adaa-polsl_RuleKit-bdcddd -P ubuntu-20.04=catthehacker/ubuntu:act-20.04-20240822 -P ubuntu-22.04=catthehacker/ubuntu:act-22.04-20240822 -P ubuntu-latest=catthehacker/ubuntu:act-latest-20240822workflow
CI log
@ChristopherHX commented on GitHub (Oct 12, 2024):
My backlog for act is full for the next months
I don't get this message inside this action..
::error::connect ENETUNREACH 2606:4700:4400::6812:23d4:443My internet service provider can connect to that ipv6 outside of docker, inside docker e.g. curl instantly skips it via
Immediate connect fail for 2606:4700:4400::6812:23d4: Network unreachableand uses ipv4 shown in curl running in a simple alpine container.curl verbose log / act log working
act-log same device
You should really upgrade this action.....
This is my successful test
@xingzhang-pku commented on GitHub (Oct 14, 2024):
Thank you for your response and your time. I believe the issue might be on my end. @ChristopherHX