tailscale / tailscale/github-action
tailscale does not turn on if we are using "container" within the github workflow
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 938
- Forks
- 137
- PR merge metrics
- No merged PRs in 30d
Description
to reproduce, see the workflow example :
name: tailscale
on:
push:
branches:
- main
pull_request:
branches:
- '*'
jobs:
build:
runs-on: ubuntu-latest
container: ubuntu:latest
steps:
- name: Check out code
uses: actions/checkout@v4
- name: install curl dependency
run: apt-get update && apt-get install curl sudo -y
- name: Tailscale Action
uses: tailscale/github-action@v2
with:
oauth-client-id: ${{ secrets.TS_OAUTH_CLIENT_ID }}
oauth-secret: ${{ secrets.TS_OAUTH_SECRET }}
tags: tag:ci
- name: check for hello.ts.net in netmap
run:
tailscale status | grep -q hello
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.
Research direction
Start with the provided GitHub Actions workflow, especially the job-level container and the Tailscale Action step, and reproduce the failure with the example configuration. Trace how the action starts Tailscale in a containerized job and verify the result with the final tailscale status | grep -q hello check. Done means the action connects successfully and the expected device appears in the netmap.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100