Trouble with action when using within docker container - Solved?
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, github-actions
- Domain
- ci-cd, documentation
Research direction
Review the repository's current documentation and the container workflow shown in the issue. Confirm when the Tailscale action requires a privileged container, then document the relevant configuration and verify that the example addresses the reported daemon startup failure.
Written by the indexing model from the issue text.
Description
Hello,
Given:
jobs:
tests:
timeout-minutes: 30
runs-on: ubuntu-latest
container:
image: ghcr.io/some-image:latest
volumes:
- /var/run/docker.sock:/var/run/docker.sock
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Tailscale
timeout-minutes: 5
uses: tailscale/github-action@v4
with:
oauth-client-id: ${{ secrets.TS_OAUTH_CLIENT_ID }}
oauth-secret: ${{ secrets.TS_OAUTH_SECRET }}
tags: tag:test-bench
We get this error in a CI:
Error: tailscaled daemon did not become ready within timeout, last error: tailscale failed with exit code 1
Digging, I realized the action try to start the application via systemctl? Or at least when I tried used v3 (which gave me the hint). Which does not work on 'default' docker images.
So - I saw somewhere to add options: --privileged as such
container:
image: ghcr.io/some-image:latest
volumes:
- /var/run/docker.sock:/var/run/docker.sock
options: --privileged
Now it works!
My issue is there was no doc I found explaining this issue - even the Tailscail AI was of no use. So I guess my issue is can you document this somewhere?
Please enlighten me if the documentation is somewhere or if there's a better solution.
Thanks
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·