Docker Build Action can't push to Tailscale-based registry
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, github-actions
- Domain
- devops, infrastructure, networking
Research direction
Reproduce the workflow using tailscale/github-action, docker/setup-buildx-action, and docker/build-push-action against the Tailscale-hosted registry. Start by comparing connectivity from tailscale status, curl, docker pull, and the buildx push step. Done means identifying the required buildx networking or proxy configuration and documenting or implementing a working workflow.
Written by the indexing model from the issue text.
Description
I strung together a github actions job with the steps:
tailscale/github-actiondocker/setup-qemu-actionsigstore/cosign-installdocker/setup-buildx-actionactions/checkoutdocker/metadata-actiondocker/build-push-action
(2-7 are pretty much default multi-platform image build pipeline github gives you.)
On my tailnet, I'm running the registry:2 container.
The problem is that when build-push-action goes to push, it can't connect:
ERROR: failed to solve: failed to push registry.redacted.ts.net/repo:tag: failed to do request: Head "https://registry.redacted.ts.net/v2/repo/blobs/sha256:9b215f6cf4b06c007e35fcc4c41c620c3728d5135472a1dd6390bb0d1dccbcd5": dial tcp: lookup registry.redacted.ts.net on 168.63.129.16:53: no such host
Adding some debug steps, I've determined:
tailscale statusruns and shows a bunch of machinescurl -iL http://registry.redacted.ts.net/v2/_catalogshows a blob of JSON from the registrydocker pullcan pull from that registry
I'm not sure if I need to set buildx to use host networking (similar to https://github.com/tailscale/github-action/issues/101#issuecomment-1889694427) or if I should set up proxy settings, or if Docker in GitHub Actions is just Weird™️.
- 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
copse-dev/agent-pane#2953 ·
-
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 ·