Skip to content

feat(install): LENS_IMAGES=pull installs a release from its prebuilt images - #575

Merged
adeelahmad merged 4 commits into
mainfrom
claude/project-thread-o74dm3
Oct 18, 2026
Merged

adeelahmad merged 4 commits into
mainfrom
claude/project-thread-o74dm3

Conversation

@adeelahmad

Copy link
Copy Markdown
Owner

Requested by Adeel · project thread

Description

Before: the install line always builds Lens's images on the machine, which is slow on a Raspberry Pi, even though each release now publishes them (#557).

After: curl … | LENS_IMAGES=pull sh downloads a release's prebuilt images (amd64 or arm64) and starts them, with no build. With no LENS_REF, a new install gets the newest release. The choice is kept in .env, so running the line again and one-click upgrades from Settings › Updates keep pulling. Building stays the default, and Lens is still built when the code is a branch (an install that follows main keeps following it, since a release may be older than what it runs), when EXTRAS are baked in, when the release predates prebuilt images, or when the download fails. LENS_IMAGES=build goes back to building; LENS_IMAGES_REGISTRY points at a mirror.

How: docker-compose.prod.yml takes the backend and frontend image names from LENS_BACKEND_IMAGE / LENS_FRONTEND_IMAGE (unset: the same lens-backend:prod names as before). A new docker-compose.images.yml drops their build sections. In pull mode install.sh writes the two names into .env (version from the release branch or tag the code is on, edition from LENS_TARGET), pulls them, and runs up -d --build with the override, so only optional containers that are built (MCP runner, Matterbridge) still build. Every later docker compose -f docker-compose.prod.yml … (the upgrade agent, Lens.app, by hand) sees the pulled names in .env and doesn't rebuild.

Also: lists #400 (the assistant answering about Lens itself) as built, since make requirements fails on main after v0.15.0 released it.

Motivation and Context

Queued item "prebuilt multi-arch images", started by the owner's "Start all". Flipping the default from build to pull changes an existing default, so it waits for the owner; this is the opt-in.

Steps to reproduce (if appropriate):

The new install.yml job One-line install from prebuilt images builds the images as images.yml does, pushes them to a registry on the runner, then installs a "release" (the PR's code on a v9.9.9 branch) with LENS_IMAGES=pull and checks it downloaded rather than built, runs those images, and answers. Locally (stub images in a local registry) I also checked: a re-run keeps pulling; a plain docker compose -f docker-compose.prod.yml up -d reuses the pulled images; a branch builds with a message; a missing tag falls back to building and clears the image names.

Types of changes

  • New feature (non-breaking change which adds functionality)

Checklist:

  • The title is a Conventional Commit.
  • My code follows the code style of this project (make hooks checks it on commit).
  • I added or updated tests. (install.yml images job)
  • My change requires documentation updates, and I have updated docs/ accordingly. (get-started, deployment)
  • Users need more than the title to understand it: n/a.

Done questions (AGENTS.md)

  • Goal: opt-in pull install, merged on green; the default flip is the owner's call.
  • Agents: n/a for now: an install-line option; a Settings/API switch is a follow-up (refine later).
  • Zero setup: no new prerequisite; one optional variable.
  • Fewest clicks: one variable, kept for later runs.
  • Configurable: in the install line and .env only for now; a switch in Settings › Updates is refine-later.
  • Light: no build on the Pi when pulling.
  • Private and secure: threat model gains a row for the prebuilt images (built from the tag with GITHUB_TOKEN, pulled over TLS by version tag).
  • Cost: no paid service.
  • User decides: default unchanged (build); existing installs unaffected unless they set it.
  • Upgrades: no stored-data change; unset variables keep today's image names.
  • Honest: docs say building is the default and when Lens still builds.
  • Tests, docs and generated files updated.
  • Open standards: OCI images; no new dependencies.
  • Reported with evidence. Refine later: a Settings/API switch, install.ps1 support, images for the optional containers.
  • Reuse: Compose's own override files and !reset; existing install.sh helpers.

Local CI: ci/local-ci.sh --jobs pre-commit,title passed; shellcheck and actionlint clean; threat model validator agrees.


Generated by Claude Code

@adeelahmad adeelahmad self-assigned this Oct 18, 2026
adeelahmad pushed a commit that referenced this pull request Oct 18, 2026
…leased)

The same change as #575, so the requirements check passes here.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015ZmJ29Kc4iXuyKqCRifAH5
Main now lists questions about Lens itself as built, so the duplicate
README line and requirements row from this branch are dropped.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014ZVBXSKSgEGnPsjq3WHhVZ
@adeelahmad
adeelahmad merged commit 49ffdd7 into main Oct 18, 2026
21 checks passed
@adeelahmad
adeelahmad deleted the claude/project-thread-o74dm3 branch October 18, 2026 09:40
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