BundleDock
BundleDock packages official stable prebuilt tools and runtimes as OCI volume carriers for shared, read-only use in Linux development containers. Each bundle has its own catalog, lock, image and volume. Stock language images supply the consumer environment; the toolbox supplies common utilities alongside them. The supported bundle platforms are Linux AMD64 and ARM64. See each guide for its consumer requirements and measured runtime coverage.
The public CLI is bdock. For development, use make run ARGS="--help";
after an approved local build, run bin/bdock --help. Existing CLI users should
replace bundledock invocations with bdock; no compatibility alias is shipped.
The BundleDock project name, repository, image references and volume paths stay
the same.
Bundles
Published version badges link to quay.io . Node badges show the upstream version recorded by the latest merged publication update; packaging revisions remain in the bundle guides.
Utilities
| Bundle | Purpose and guide | Published version | Publication workflow |
|---|---|---|---|
| Toolbox | Development CLIs and common utilities | 
|
|
Runtimes
| Bundle | Purpose and guide | Published version | Publication workflow |
|---|---|---|---|
| Bun | Bun runtime and bunx | 
|
|
| Node.js | Node.js LTS with npm/npx | 
|
|
| Node.js Current | Node.js Current with npm/npx | 
|
|
Infrastructure
| Bundle | Purpose and guide | Published version | Publication workflow |
|---|---|---|---|
| OpenTofu | Official OpenTofu CLI — source prepared, publication pending | 
|
|
Editors
| Bundle | Purpose and guide | Published version | Publication workflow |
|---|---|---|---|
| code-server | Standalone browser editor | 
|
|
Agents
| Bundle | Purpose and guide | Published version | Publication workflow |
|---|---|---|---|
| Antigravity | Official Antigravity CLI | 
|
|
| Claude Code | Official Claude CLI | 
|
|
| Codex | Official Codex package | 
|
|
The three agent carriers have verified publication receipts in their guides. The published toolbox below matches the current catalog without those agents. Consumer activation follows the consumer project’s instructions.
Documentation — quick start and guides for using, maintaining, and publishing each bundle.
The shared publication workflow badge reports the latest controller run. Individual bundle publication and version evidence remains in each bundle guide.
CLI releases
The bdock CLI is released as archives for Linux AMD64, Linux ARM64 and macOS ARM64 by a
tag-driven CI workflow (tags bdock/vMAJOR.MINOR.PATCH, separate from the OCI image tags).
No CLI release has been published yet. The owner procedure is docs/releasing.md in the
repository; OCI images are published separately.
Quick start
You need Docker running and a local clone of this repository. Pull the published toolbox by its immutable multi-platform index digest, then initialize its volume:
TOOLBOX_IMAGE=quay.io/bundledock/toolbox@sha256:c7715f6a2cae2812dcaf847185427080f2ab73097aa392393d427e460afed402
docker pull "$TOOLBOX_IMAGE"
make bundle-volume BUNDLE=toolbox IMAGE="$TOOLBOX_IMAGE"
This example is toolbox version 2026.10.18-b2, published from
dce172b73a78d3a816dbfbf60129415156ad6a31
in publication run 39156619187, attempt 1
.
The initializer prints Volume: bundledock-toolbox-<full image ID>; use that volume name below:
docker run --rm -it \
--mount type=volume,src=<printed-volume-name>,dst=/opt/bdock/toolbox,readonly,volume-nocopy \
--env DISABLE_UPDATES=1 --env DISABLE_AUTOUPDATER=1 \
mcr.microsoft.com/devcontainers/go:2-1.27-trixie \
sh -c 'export PATH="/opt/bdock/toolbox/bin:$PATH"; exec bash'
Existing images keep their original initializer source; their relative volume
contents can be mounted at /opt/bdock/toolbox. Future carriers include a temporary
/opt/bundledock -> /opt/bdock link. Consumers needing legacy paths create that
link during privileged setup; see bundle roots
.
Keep credentials, configuration, caches, and environments in writable home directories or private volumes. The toolbox is read-only and contains no credentials.
The OCI image is a volume carrier built from scratch. Run its tools in a
compatible consumer, which supplies Git, certificates, terminfo, and system
libraries. See consumer requirements
for runtime details. Anchorage owns the separate devcontainer integration and
its image and volume pins
. Follow that
consumer project’s instructions to adopt a published bundle.
Toolbox source catalog
The current source catalog pins 33 tools, with these companion commands. This describes the desired source inventory; published images retain their own pins:
| Use | Tools |
|---|---|
| GitHub workflows | GitHub CLI (gh)
, gh stack extension
|
| Search and structured data | ripgrep (rg)
, fd (fd, fdfind)
, ast-grep
, jq
, yq
|
| Interactive filtering and file viewing | fzf , bat , lsd , zoxide |
| Markdown preview | Leaf |
| Development utilities | ShellCheck
, shfmt
, just
, Ruff
, delta
, watchexec
, hyperfine
, age
, git-cliff
, Difftastic (difft)
, jsonschema-cli
|
| OCI registries | regctl |
| Python environments | uv and uvx |
| Spec-driven project setup | Spec Kit (specify, pinned runtime launcher)
|
| Shells and terminal workspaces | Herdr
, Fish
, Starship
, Nushell (nu)
, tmux
|
| Quality and security | typos , lychee , Gitleaks , TruffleHog , Trivy , Syft , actionlint , Hadolint , pinact , zizmor , Cosign |
| Optional version manager | mise |
| Terminal editor | Helix (hx)
|
| Static sites | Hugo (standard) |
| Process monitoring | bottom (btm)
, btop
|
See pinned versions and upgrades . Agents are supplied by the separate Codex , Antigravity and Claude Code bundles. Codex retains its native helpers while omitting optional voice resources.
Contributing
See CONTRIBUTING.md for contribution and verification guidance. Participation in the BundleDock community follows our Code of Conduct .
Documentation
Browse the documentation site or read the Markdown sources in this repository:
- CLI and quick start (source ): pull the published toolbox and use its shared volume.
- Tool catalog and upgrades (source ): pinned versions and lock updates.
- Architecture (source ): shared volumes, rollback, and consumer requirements.
- Development and verification (source ): CLI commands, checks, and recorded coverage.
- Publication (source ): Quay setup, updater approval and manual exact-SHA publication.
The CI workflow runs formatting, source tests and vet. Maintainers can find build approval, publication and verification details in the publication guide and verification record .
BundleDock is licensed under the European Union Public Licence 1.2 (EUPL-1.2) .
Upstream tool notices are kept in bundles/toolbox/licenses ; brand licensing and asset provenance are documented in brand/README.md . BundleDock’s source and full-history provenance are independent of image publication and consumer activation.