Skip to content

fix(relay): route China deploys through mirrors - #2010

Merged
bobleer merged 1 commit into
GCWing:mainfrom
bobleer:bob/fix-relay-cn-mirror-routing
Aug 3, 2026
Merged

fix(relay): route China deploys through mirrors#2010
bobleer merged 1 commit into
GCWing:mainfrom
bobleer:bob/fix-relay-cn-mirror-routing

Conversation

@bobleer

@bobleer bobleer commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • propagate the resolved Auto/China/Global route through Docker installation, detached deployment, the published-binary runtime image, and source-build fallback
  • pass the China apt mirror into the generated runtime Dockerfile while retaining the trixie glibc compatibility floor
  • add a wizard override for inaccurate cloud IP geolocation, route-reason logging, bounded apt retries/timeouts, documentation, and regression coverage

Root cause

The Docker daemon registry mirror accelerated the base-image pull, but the generated published-binary Dockerfile still ran apt inside the image against deb.debian.org. Host apt settings cannot affect that build step, so a correctly detected mainland-China host could still stall or fail.

Verification

  • cargo test -p bitfun-services-integrations --features remote-ssh,remote-ssh-concrete relay_deploy --lib (32 passed)
  • cargo check --workspace
  • pnpm run type-check:web
  • pnpm run lint:web
  • pnpm run i18n:audit
  • bash -n src/apps/relay-server/{mirror.sh,release-download.sh,deploy.sh}
  • git diff --check

Live Docker image building was not available locally because the Docker daemon is not running; the build-argument path is covered by a shell-backed regression test.

@bobleer
bobleer merged commit 3f8e5e6 into GCWing:main Aug 3, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant