mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #1559] Embedded artifact server inaccessible on clients with Zscaler Client Connector running #785
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#785
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 @isometry on GitHub (Jan 13, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/1559
Bug report info
Command used with act
Describe issue
On client devices with the Zscaler Client Connector installed, the outbound IP is always
100.64.0.1(CGNAT). Unfortunately, on non-Linux devices, this address is unroutable from Docker Desktop's embedded VM or the containers running on it, thus making the embedded artifact server inaccessible.Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
I've already developed a patch to address this issue: PR incoming.
@isometry commented on GitHub (Jan 14, 2023):
#1560 provides a simple workaround for this issue by allowing the user to override the artifact server bind address.
@Francisco-RP commented on GitHub (Apr 11, 2023):
I'm having this issue now with ZScaler. The rest of my job runs and works, it's only my download and upload artifacts steps that fail
So what exactly should by passing to
--artifact-server-addrto get it work? because I tried setting it to127.0.0.1but then I just started getting:This is my command:
New to
actand not super experienced with Docker so no idea what to do to get this to work. Do I need to be mapping ports or something?This is what my custom-act-image looks like and it seems to be working because node installs and runs.
@Francisco-RP commented on GitHub (Apr 12, 2023):
I solved my issue. I just used my host ip address (
--artifact-server-addr $(ipconfig getifaddr en0)) and that worked.@isometry commented on GitHub (Apr 13, 2023):
Exactly, yes. Sorry not to have responded before.
@ndemayo-bah commented on GitHub (May 16, 2024):
This just saved me so much headache, thank you internet stranger!
@higoramorimkroger commented on GitHub (Dec 2, 2024):
@Francisco-RP I tried your solution but I'm still getting "socket hang up". Do you have any other suggestion, please?