Skip to content

Switch container registry to Google Artifact Registry and honour uv.l…#256

Open
mgsalem wants to merge 2 commits into
mainfrom
feat/switch-to-gcp-artifact-registry
Open

Switch container registry to Google Artifact Registry and honour uv.l…#256
mgsalem wants to merge 2 commits into
mainfrom
feat/switch-to-gcp-artifact-registry

Conversation

@mgsalem
Copy link
Copy Markdown
Collaborator

@mgsalem mgsalem commented May 14, 2026

PR Type

Other (CI / build pipeline)

Short Description

Switches container image publishing from Docker Hub to Google Artifact Registry, authenticated via Workload Identity Federation.
Registry coordinates are parameterized through GitHub Actions variables.

Also fixes the issue where vllm.Dockerfile / sglang.Dockerfile ignored uv.lock (because uv pip install doesn't read lockfiles — only uv sync does). The new install step exports uv.lock to a pinned requirements.txt and installs with --no-deps, so the image matches the lockfile.

Tests Added

No unit tests — change is CI/build-pipeline only. Verified by:

mgsalem and others added 2 commits May 14, 2026 13:24
…ock at build time

- docker.yml: auth via WIF, push to GAR. Registry coordinates come from
  GCP_AR_REGION/GCP_PROJECT_ID/GCP_AR_REPOSITORY variables and
  GCP_WIF_PROVIDER/GCP_WIF_SERVICE_ACCOUNT secrets.
- vllm.Dockerfile, sglang.Dockerfile: install pinned to uv.lock via
  'uv export --frozen | uv pip install --no-deps' (uv pip install
  alone ignores the lockfile). Adds a build-time import canary.
- README and docs/index: point to GAR.
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.

2 participants