homelab/stack
1
0
Fork 0
Code Issues 70 Pull Requests 1 Actions Packages Projects 1 Releases Wiki Activity

[P9] Add CoreDNS service for container name resolution #101

New Issue
Closed
opened 2026-03-22 15:46:25 +00:00 by kert · 0 comments
kert commented 2026-03-22 15:46:25 +00:00
Owner
Copy Link

Problem

Containers (especially buildkit) cannot resolve *.homelab.fhirworx.io because there is no DNS service in the stack. We rely on extra_hosts hacks per-service which don't propagate to dynamically created containers like buildkit builders.

Solution

Add a CoreDNS (or dnsmasq) service that:

  • Resolves *.homelab.fhirworx.io → $HOST_IP
  • Forwards everything else to upstream DNS
  • Runs on the gateway network so all containers can reach it

Acceptance criteria

  • CoreDNS service in compose.yml with a Corefile
  • Wildcard homelab.fhirworx.io zone pointing to HOST_IP
  • Upstream forwarding for all other queries
  • Docker daemon configured to use this resolver (dns in daemon.json)
  • Remove extra_hosts from woodpecker-server (no longer needed)
  • Verify: docker run --rm alpine nslookup gitea.homelab.fhirworx.io resolves
## Problem Containers (especially buildkit) cannot resolve `*.homelab.fhirworx.io` because there is no DNS service in the stack. We rely on `extra_hosts` hacks per-service which don't propagate to dynamically created containers like buildkit builders. ## Solution Add a CoreDNS (or dnsmasq) service that: - Resolves `*.homelab.fhirworx.io` → `$HOST_IP` - Forwards everything else to upstream DNS - Runs on the `gateway` network so all containers can reach it ## Acceptance criteria - [ ] CoreDNS service in compose.yml with a Corefile - [ ] Wildcard `homelab.fhirworx.io` zone pointing to HOST_IP - [ ] Upstream forwarding for all other queries - [ ] Docker daemon configured to use this resolver (`dns` in daemon.json) - [ ] Remove `extra_hosts` from woodpecker-server (no longer needed) - [ ] Verify: `docker run --rm alpine nslookup gitea.homelab.fhirworx.io` resolves
kert added this to the P9: CI/CD Unification milestone 2026-03-22 15:46:25 +00:00
kert added the ci label 2026-03-22 15:46:25 +00:00
kert closed this issue 2026-03-23 17:56:49 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
REST API (FastAPI)
 auth
Authentication and authorization
 bib
Bibliography, Zotero, citations
 ci
CI/CD pipelines and Woodpecker plugins
 cli
CLI commands and UX
 cloud
Cloud provider abstraction (AWS, GCP, Azure, self-hosted)
 config
Configuration and wiring
 data
Data loading, CCLF, BCDA, seeds
 databricks
Databricks jobs and deployment
 docs
Documentation and generated references
 image:api
image:docs
image:mc
image:notebooks
image:zotero
infra
lakehouse
Nessie, Polaris, Trino, Iceberg
 llm
llm module — local RAG over comments + Zotero corpus
 notebooks
marimo notebook errors (auto-filed by nb-watcher/nb-integration)
 packaging
Python packaging, optional deps, build system
 pfs
pipeline
Pipeline execution and validation
 pipeline:ci
pipeline:deploy
pipeline:harden
pipeline:infra-ci
pipeline:rebuild-all
pipeline:release
qpp
quality
Testing, coverage, error handling
 step:build
step:deploy
step:hadolint
step:lint
step:publish
step:scan
step:test
step:validate
styles
Charts, figures, visual theming
 tree
Project directory structure and file organization
No Label ci
Milestone
No items
No Milestone P9: CI/CD Unification
Projects
Clear projects
No project
Assignees
Clear assignees
kert renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: homelab/stack#101
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?