Skip to content

Latest commit

 

History

History
58 lines (38 loc) · 5.41 KB

README.md

File metadata and controls

58 lines (38 loc) · 5.41 KB

Image build downloads

The shared deploy/scripts/build-image.sh helper builds the runtime rootfs and all-in-one node image for make build and make standalone. Downloads use official repositories and pinned upstream releases by default.

Package repositories

Select mirrors for one invocation without changing host package-manager or Docker daemon configuration:

make standalone AKERNEL_BUILD_MIRROR=aliyun
# The same option applies to make build.

AKERNEL_BUILD_MIRROR accepts official (the default) or aliyun. The Aliyun preset covers Ubuntu APT, Debian APT in the Go/Rust builder stages, and Python packages in the optional Python runtime profile. Ubuntu ARM64 selects ubuntu-ports; AMD64 selects ubuntu. APT source rewriting preserves suites, components, signing keys and signature verification, and changes only recognized official repository URIs in .list and .sources files. Third-party repositories retain their own URLs. Go keeps its official proxy unless the caller explicitly sets GOPROXY; module checksum verification stays enabled.

APT uses the Aliyun HTTP endpoints because minimal Ubuntu images do not yet contain CA certificates; APT still verifies signed repository metadata and package hashes. Python uses HTTPS. An explicit HTTPS APT mirror requires a base image with a populated CA trust store; TLS verification is never disabled. See the official Ubuntu, Ubuntu Ports, Debian, Debian security, and PyPI mirror documentation.

Nonempty caller overrides take precedence over the preset. These public repository URLs are passed as Docker build arguments, so they must not contain credentials, query parameters or fragments:

Environment variable Scope
AKERNEL_APT_UBUNTU_MIRROR Ubuntu AMD64 archive and security repository root
AKERNEL_APT_UBUNTU_PORTS_MIRROR Ubuntu ARM64 ports repository root
AKERNEL_APT_DEBIAN_MIRROR Debian archive repository root
AKERNEL_APT_DEBIAN_SECURITY_MIRROR Debian security repository root
PIP_INDEX_URL Python profile pip installs, uv package installs and venv seeds
GOPROXY Go module downloads; public URL with optional ,direct, or direct/off

Python and Go repository selections are used only during builds; no mirror environment setting is added to the sandbox runtime. Selected APT repository URLs remain in the built images. Mirrors may lag upstream, and failures remain visible instead of automatically switching sources. Docker base-image pulls, GitHub release assets, GitLab source, Cargo packages, NVIDIA repositories and uv-managed Python interpreter downloads use their existing sources. Docker registry mirrors belong to the daemon configuration.

Pinned release files

Package mirrors do not serve the large core wheel or other GitHub release files. For an explicitly selected artifact cache or an unreleased build, the helper accepts these URL/checksum pairs:

Environment variables Build stage Equivalent helper options
RRT_RUNTIME_URL, RRT_RUNTIME_SHA256 RRT binary --rrt-runtime-url, --rrt-runtime-sha256
OPEN_YR_CORE_WHEEL_URL, OPEN_YR_CORE_WHEEL_SHA256 Control-plane wheel --open-yr-core-wheel-url, --open-yr-core-wheel-sha256
OTELCOL_CONTRIB_URL, OTELCOL_CONTRIB_SHA256 OTel collector archive --otelcol-contrib-url, --otelcol-contrib-sha256

Each pair is validated before either image build; downloads retain checksum and native ELF architecture checks. A mirror of the same release must use its existing pinned checksum. Core wheel URLs must retain a valid wheel filename. Runtime versions and gVisor, runc, Firecracker and distill-fs pins continue to come from their existing manifests.

Source version/revision labels and artifact URL overrides are declared near their uses so changing those inputs preserves preceding dependency layers.

Build proxy and network

Export proxy variables for an endpoint reachable from the Docker builder, then opt into forwarding them:

make standalone AKERNEL_BUILD_PROXY=true
# The same option applies to make build.

AKERNEL_BUILD_PROXY accepts true or false and defaults to false. The helper forwards the predefined uppercase and lowercase HTTP_PROXY, HTTPS_PROXY, NO_PROXY, and ALL_PROXY build arguments by name to both builds. Keep their values out of command arguments, logs, saved configuration, and Dockerfile ARG declarations. Docker may also populate proxies from its client configuration; omitting this option does not disable those settings.

AKERNEL_BUILD_NETWORK accepts default (the default) or host. Selecting host passes --network host to both builds, allowing RUN instructions to reach host-local services, including a localhost proxy with OrbStack. These options affect image-build downloads only; standalone containers and sandbox traffic retain their deployment settings.

OrbStack can follow macOS proxy settings independently of container environment variables. An empty proxy environment or curl --noproxy '*' alone does not establish a direct outbound connection. Build and standalone helpers do not change host-wide proxy settings.