Docker-compose to use the network host but could not resolve tailscale network domain
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, docker-compose, github-actions, node.js
- Domain
- build-system, devops, networking
Research direction
Start by reproducing the workflow in the issue, including the Tailscale action, the curl check, and docker-compose build xxx. Compare the runner's successful host lookup with the Dockerfile's npm ci request to the tailnet registry. Done means the compose build can resolve and access the registry domain, or the missing configuration is documented.
Written by the indexing model from the issue text.
Description
Hi,
I've this job auth successfully with my tailscale network
on the github runner could interact, solved domain from my machine in tail net..
however, the docker-compose could not resolve the tailscale domain by magic DNS during the docker-compose build
is there any missing
jobs:
image:
runs-on: ubuntu-latest
strategy:
matrix:
app: [xxx]
steps:
- name: Tailscale
uses: tailscale/github-action@v2
with:
oauth-client-id: ${{ secrets.TS_OAUTH_CLIENT_ID }}
oauth-secret: ${{ secrets.TS_OAUTH_SECRET }}
tags: "tag:k8s"
version: 1.52.0
- run: |
tailscale status
curl http://xxx.tailxxxx.ts.net:8888
- run: |
... docker-compose build xxx
the dockerfile looks like:
ARG NODE_VERSION=12
###
FROM node:$NODE_VERSION as builder
ARG NEXUS_NPM_TOKEN
ARG NEXUS_CERT_FILE
RUN npm config set //xxxxx.tailxxx.ts.net:8080/repository/npm-playstudios/:_authToken $NEXUS_NPM_TOKEN \
&& npm config set @psa:registry http://xxxxx.tailxxx.ts.net:8080/repository/npm-playstudios/
...
RUN ["npm", "ci"]
log:
npm ERR! code E400
5.780 npm ERR! 400 Bad Request - GET http:
- 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 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug v2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/inspector#2458 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
railmapgen/rmp-gallery#4068 ·
-
Mend: dependency security vulnerability status: needs triage 🕵️♀️
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
carbon-design-system/ibm-products#9907 ·