Bundle overview
BundleDock packages pinned development tools into OCI carrier images for Linux AMD64 and ARM64. Initialize a named volume from a carrier, then mount the tools read-only in a compatible development container. The carrier supplies files; your consumer container supplies the operating system and writable workspace. Use stock language images for language toolchains and add the toolbox for common utilities. See the quick start and consumer requirements .
Each bundle has its own desired package list, catalog, verified lock, image,
volume and /opt/bdock/<bundle> root. A package is an upstream tool or
runtime inside a bundle; a bundle is the independently versioned carrier that
ships those packages. Select bundles independently with BUNDLE=<bundle> when
using the Makefile. Keep HOME, credentials, caches, configuration and project
state writable outside these immutable roots. Each guide explains its specific
consumer requirements and verification limits.
Utilities
| Bundle | Purpose and guide | Registry tags |
|---|---|---|
OpenTofu (opentofu) |
Infrastructure CLI (tofu)
; providers and project state stay with the consumer. |
OpenTofu tags |
Toolbox (toolbox) |
Common development utilities , including search, shells, GitHub/registry tools and source checks. | Toolbox tags |
Runtimes
| Bundle | Purpose and guide | Registry tags |
|---|---|---|
Bun (bun) |
Bun runtime and bunx . | Bun tags |
Node.js (node) |
Node.js LTS with npm/npx . | Node LTS tags |
Node.js Current (node-current) |
Node.js Current with npm/npx , resolved independently from LTS. | Node Current tags |
Node LTS and Current have separate locks and volumes, but share the
quay.io/bundledock/node repository. Their lts and current aliases select
the published channels; see the guides for immutable digest references.
Editors
| Bundle | Purpose and guide | Registry tags |
|---|---|---|
code-server (code-server) |
Standalone browser editor ; starting and exposing its service is a consumer choice. | code-server tags |
Agents
| Bundle | Purpose and guide | Registry tags |
|---|---|---|
Antigravity (agy) |
Official Antigravity CLI . | Antigravity tags |
Claude Code (claude) |
Official Claude CLI . | Claude Code tags |
Codex (codex) |
Official Codex package and native helpers . | Codex tags |
The agent carriers have published receipts in their guides. The published toolbox carrier excludes these agents. Choose the exact carrier recorded in the guide and follow your consumer project’s adoption instructions.
Source inventory and published images
A guide’s generated inventory describes its current source lock. Its published bundle section records a specific image version, immutable index digest, exact source commit and publication run. These can differ: editing a lock or merging source does not rebuild an existing carrier. Follow those receipts when choosing an image; no overview table duplicates the managed package versions or digests.
See each guide’s published bundle section, including the OpenTofu receipt , for the exact published source and immutable image reference.
Quay tag listings show published registry state. Moving aliases such as stable,
latest, lts and current can change; use an immutable index digest for a
reproducible consumer. Single-package carriers use upstream versions with a
packaging revision, while toolbox versions use the documented date/run scheme.
See publication and versioning
,
lock upgrades
and
development verification
for the canonical procedures.
Builds, publication, tagging and consumer activation each retain their explicit
approval requirements described in those guides.