Repository navigation
feat(install): LENS_IMAGES=pull installs a release from its prebuilt images - #575
Merged
Merged
Conversation
…images Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014ZVBXSKSgEGnPsjq3WHhVZ
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014ZVBXSKSgEGnPsjq3WHhVZ
…s built Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014ZVBXSKSgEGnPsjq3WHhVZ
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
21 of 23 tasks
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 shdownloads a release's prebuilt images (amd64 or arm64) and starts them, with no build. With noLENS_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 followsmainkeeps following it, since a release may be older than what it runs), whenEXTRASare baked in, when the release predates prebuilt images, or when the download fails.LENS_IMAGES=buildgoes back to building;LENS_IMAGES_REGISTRYpoints at a mirror.How:
docker-compose.prod.ymltakes the backend and frontend image names fromLENS_BACKEND_IMAGE/LENS_FRONTEND_IMAGE(unset: the samelens-backend:prodnames as before). A newdocker-compose.images.ymldrops 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 fromLENS_TARGET), pulls them, and runsup -d --buildwith the override, so only optional containers that are built (MCP runner, Matterbridge) still build. Every laterdocker compose -f docker-compose.prod.yml …(the upgrade agent, Lens.app, by hand) sees the pulled names in.envand doesn't rebuild.Also: lists #400 (the assistant answering about Lens itself) as built, since
make requirementsfails 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 imagesbuilds the images as images.yml does, pushes them to a registry on the runner, then installs a "release" (the PR's code on av9.9.9branch) withLENS_IMAGES=pulland 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 plaindocker compose -f docker-compose.prod.yml up -dreuses the pulled images; a branch builds with a message; a missing tag falls back to building and clears the image names.Types of changes
Checklist:
make hookschecks it on commit).imagesjob)docs/accordingly. (get-started, deployment)Done questions (AGENTS.md)
.envonly for now; a switch in Settings › Updates is refine-later.!reset; existing install.sh helpers.Local CI:
ci/local-ci.sh --jobs pre-commit,titlepassed; shellcheck and actionlint clean; threat model validator agrees.Generated by Claude Code