Skip to content

infra(ai): Vercel container registry is full – AI service builds fail #98

Closed

Description

@Fluory

What happened

The production build of requestflow-ai for the merge of #95 (3e9ba75, deployment dpl_215DLzzxTp6CSK9bAEsYg6Jyx6ai) failed while pushing its image:

denied: repository has reached the maximum allowed number of images (vcr.vercel.com/doc-edit/requestflow-ai/dockerfile)

Production still serves the last good image (#94, dpl_8KqsWUURaQ3wkWF5HnxKfKko6pQs) – nothing is down. But the next change under services/ai/ would not deploy.

Cause

Every push – main and every preview branch – builds and pushes a new AI image, also when nothing under services/ai/ changed (#95 touched only the web app). The registry of the Hobby team has a maximum number of images.

Proposed fix (needs the orchestrator – account action)

  • Prune old images in the Vercel dashboard (project requestflow-ai → Sandboxes → Container Registry); keep the image of the current production deployment and one rollback candidate
  • Build the AI project only when its root changed: "ignoreCommand": "git diff --quiet HEAD^ HEAD -- ." in services/ai/vercel.json (root directory of the project), plus a note in the deploy docs
  • Verify: a web-only PR shows the AI build as skipped; a PR touching services/ai/ builds and /healthz answers

Security/Privacy affected?

No.

Activity

  1. Fluory commented on Sep 28, 2026

    @Fluory
    OwnerAuthor

    Also observed 2026-09-28 ~20:00: both Vercel projects answer "Deployment rate limited – retry in 24 hours" (Hobby daily deployment limit) after a day with many PR pushes – every push deploys web and AI preview. The ignoreCommand above would also halve that consumption for PRs that do not touch services/ai/. Nothing is down: production keeps the last good deployments; merges of today deploy once the limit resets.

  2. self-assigned this
    on Sep 28, 2026
  3. Fluory commented on Sep 28, 2026

    @Fluory
    OwnerAuthor

    Claimed by @Fluory on branch claude/fix-ai-build-skip-98 for the repo-side part (build only when services/ai/ changed). Pruning the registry stays an account action for the orchestrator – commands in the PR.

  4. Fluory commented on Oct 11, 2026

    @Fluory
    OwnerAuthor

    Erledigt (2026-10-11):

    🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething is broken

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions