Installing without internet access
This guide describes how to install a Legacy Modernization release on a host that cannot pull container images from an external registry.
Choose A Release Artifact
Each release publishes one airgapped bundle:
legacy-modernization-<version>-airgap-core.tgz
legacy-modernization-<version>-airgap-core.tgz.sha256
It carries everything the running stack needs, Repave IDE included.
Releases before this one also published a separate
-airgap-session-bases.tgz bundle holding three per-stack Repave IDE images.
That bundle no longer exists: every agent job and every Repave IDE session now
runs the same image, the agent runner, which is already in the core bundle.
The old undifferentiated legacy-modernization-<version>-airgap.tgz (before
0.1.84) no longer exists either. The core bundle's name was kept distinct so an
operator following an older runbook cannot mistake one for the other.
Core bundle
The Compose files, install docs, image metadata, checksums, and the first-party images the running stack needs:
images/server-<version>.tar.gz
images/agent-runner-<version>.tar.gz
images/claude-mem-server-<version>.tar.gz
images/legacy-desktop-<version>.tar.gz
images/legacy-recorder-<version>.tar.gz
images/dind-<version>.tar.gz
images/installer-<version>.tar.gz
installer is not part of the running stack — it's what you run to install
and upgrade — but ships here for the same reason everything else in this list
does: this host cannot pull an image later.
agent-runner is the one runtime image: it runs every agent job, every
Repave IDE session, every target-stack preview and every implementation
runtime. It carries Node 22, JDK 21 with Maven and Gradle, .NET 10, Python 3,
code-server with the Claude Code, Codex and Repave extensions, the Claude Code,
Codex and repave CLIs, a Docker client with Compose and buildx, and a Chrome
browser. Because agents and developers run the same image, code an agent built
and verified behaves the same when you open it in Repave IDE.
dind is the private Docker daemon each Repave IDE session runs beside it.
legacy-desktop runs a project's legacy Windows desktop app, so agents can
check scenarios against the application being replaced. Like the agent runner,
the app starts it on demand rather than through Compose.
legacy-recorder runs beside the legacy app while agents check scenarios
against it, recording the app's SQL and outbound HTTP. The app starts it on
demand too.
Third-party images: not in the bundle
Five images this release depends on are not archived in the bundle:
docker-host (alpine/socat), postgres, valkey, cli-proxy-api, and
nginx. These are unmodified upstream images we don't build, and as of
the
release pipeline no longer ships a copy of them — it still pins and records
their exact tag+digest in metadata/images.json (with bundled: false) and
metadata/release-manifest.json, so you can see precisely what this release
expects, but the archive itself is not in images/.
We assume you preload these five images yourself, the same way you would
any image this installer doesn't ship. From a connected host, pull the exact
tag+digest recorded in metadata/images.json, docker save it, and load it
on the target host before installing — or, if the host has some network
route to the images' upstream registries (docker.io, ghcr.io, wherever
cli-proxy-api's image resolves from), docker pull them there directly.
postgres and valkey are not optional — the stack cannot start without
them — so this applies to a from-scratch airgapped install of the core stack
itself, not only to the nginx/cli-proxy-api profiles.
If you previously relied on the old all-in-one bundle to install with zero
preload steps at all, that guarantee no longer holds for these five images.
The installer's --airgap preflight checks each by name and tells you which
ones are missing — it never attempts a pull on your behalf.
What Repave IDE needs offline
Nothing beyond the core bundle. Nothing is built when a session opens: a
session runs the agent runner image directly, alongside its own Docker daemon
from the dind image. There is no per-project image choice and no toolchain
setting — every project, whatever its stack, opens on the same image.
All of it used to be downloaded on the client, on each project's first "Open in
Repave IDE", from github.com, open-vsx.org, the Playwright CDN, npm and apt —
five hosts an airgapped install cannot reach. It is baked in at publish time
instead. The toolchains are baked in for the same reason, so the generated
devcontainer config requests no remote devcontainer features either.
If the image is not loaded, Repave IDE says so and names both the missing tag
and the .env key that pins it (AGENT_RUNNER_IMAGE) — there is no build to
wait for and nothing to retry. In practice agent jobs cannot run without it
either, so a deployment where agents work can open sessions.
The agent runner archive is about 2.9 GB compressed. A deployment that uses Repave IDE downloads less than it did when the IDE needed a separate image; one that never opens Repave IDE downloads somewhat more, because the IDE layer now travels with the agent runner.
When the client's codebase needs an older toolchain
The image carries one version of each toolchain — Node 22, JDK 21, .NET 10. A
provided codebase that targets an older one (Angular 14, .NET 6) will not build
in it, and no .env setting changes that. The answer is a per-client overlay
image: a thin derivation of the published agent runner that adds the legacy
Node and/or .NET SDK beside the shipped ones, built on a connected host and
loaded here like any other archive. One overlay serves agent jobs and Repave IDE
sessions alike. Repave builds it for your deployment and supplies it with the
release.
It is declared once in .env, by repository and without a tag:
AGENT_RUNNER_IMAGE_OVERLAY=repave-overlay-agent-runner-<name>
An overlay must be rebuilt and loaded here for every new version. The pin itself follows the upgrade on its own, from that declaration; an upgrade whose overlay image is missing stops and names the tag rather than reverting the deployment to the stock image .
A deployment upgraded from a release that had a separate Repave IDE overlay
(SESSION_BASE_*_IMAGE_OVERLAY=repave-overlay-session-<name>) and no agent
runner overlay is moved to repave-overlay-agent-runner-<name> automatically
during the upgrade, and the old key is removed. Load that agent runner overlay
archive for the new version before upgrading; the upgrade stops and names it if
it is missing.