tailscale / tailscale/github-action

Docker-compose to use the network host but could not resolve tailscale network domain

Open
#105 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
938
Forks
137
PR merge metrics
No merged PRs in 30d

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:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
docker, docker-compose, github-actions, node.js
Domain
build-system, devops, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.