macOS runner exit node support
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github-actions, macos
- Domain
- ci-cd
Research direction
Start by reproducing the provided workflow with tailscale/github-action@v3 on a macos-15 runner, then compare its behavior with the Linux workflow using the listed tailscale status and tailscale set commands. Done means establishing whether exit-node mode works on macOS and documenting any limitation or required configuration.
Written by the indexing model from the issue text.
Description
Hi,
I’m trying to use the tailscale/github-action in a GitHub Actions workflow running on a macOS runner (macos-15) with an exit node.
While the same workflow works fine on Linux runners, it doesn’t seem to work properly on macOS.
My questions are:
- Is exit node mode currently supported when using this action on macOS runners?
- If it is supported, are there any known limitations or required flags to make it work?
name: Use Tailscale Exit Node
on: push
jobs:
run-with-exit-node:
runs-on: macos-15
steps:
- name: before
run: |
echo "Public IP:" && curl -s https://ifconfig.me
- name: Connect to Tailscale
timeout-minutes: 3
uses: tailscale/github-action@v3
with:
oauth-client-id: ${{ secrets.TAILSCALE_OAUTH_CLIENT_ID }}
oauth-secret: ${{ secrets.TAILSCALE_OAUTH_SECRET }}
version: ${{ vars.TAILSCALE_VERSION }}
tags: ${{ vars.TAILSCALE_TAGS }}
use-cache: true
- name: Wait & list nodes
run: |
sleep 3
sudo -E tailscale status
- name: Set exit node by name
run: |
sudo -E tailscale set --exit-node="ci_exit_node" --exit-node-allow-lan-access=true
- name: after
run: |
echo "Public IP:" && curl -s https://ifconfig.me
- Dominant language
- TypeScript
- Stars
- 938
- Forks
- 137
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tailscale/github-action
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
tailscale/github-action#283 · 1 comment · 1 reaction ·
-
fr
Difficulty 3/5 1-2 days Newbie friendliness 68/100
tailscale/github-action#317 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
tailscale/github-action#316 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
tailscale/github-action#315 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
tailscale/github-action#313 · 1 reaction ·
All issues in tailscale/github-action
Similar issues
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/rig#534 ·
-
automation missing-model model-sync provider:pioneer
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
anomalyco/models.dev#7701 ·