tailscale / tailscale/github-action
Unreliable DNS during Container Builds
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 938
- Forks
- 137
- PR merge metrics
- No merged PRs in 30d
Description
I have a GitHub Actions pipeline that roughly process like so:
- Connect to a private Tailscale network using this Github Action.
- Start a docker build of a multi-stage Dockerfile where an internal python package index[1] is accessed to pull dependencies.
[1]: This package index is available within the Tailscale network and is discovered using DNS of an internal DNS server configured in Tailscale.
Step 2 occasionally fail due to DNS lookups for the package index failing, thus DNS resolving not working reliably.
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 by reproducing the two-step GitHub Actions workflow: connect to the private Tailscale network, then run the multi-stage Docker build that accesses the internal Python package index. Investigate when DNS lookups fail during the build; done means the package index resolves reliably throughout repeated builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, python
- Domain
- ci-cd, devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100