mirror of
https://github.com/hanzoai/pack.git
synced 2026-09-30 23:43:13 +00:00
zeekayandHanzo Dev
e12b42f3ec
REPO_OWNER/REPO_NAME built the GitHub API and download URLs from railwayapp/railpack, so the installer could never find a release under this fork -- hanzoai/pack has never had one. REPO_NAME did double duty as both the repository slug (used in the API and download URLs, needs to be "pack") and the installed command name (used by `which`/`rm` on uninstall, needs to stay "railpack", the actual compiled binary name per .goreleaser.yml). Collapsing both into "pack" would make uninstall run `which pack`, which on many machines resolves to the unrelated Cloud Native Buildpacks CLI. Split it into REPO_NAME (repo slug and archive-name prefix, matching the project_name pinned in .goreleaser.yml) and a new BINARY_NAME (the installed executable), and routed each use to the right one. RELEASE.md's GHCR links and package-registry URLs updated to match. Do not merge until hanzoai/pack has an actual release: push a v* tag once the prior two commits are on main and the release workflow has published the builder, runtime, and frontend images. Before that, the download URL this script builds 404s by construction. Co-authored-by: Hanzo Dev <[email protected]>
Hanzo Pack
Zero-config OCI image builder and BuildKit gateway frontend for the Hanzo Cloud.
Hanzo Pack is the zero-configuration container image builder that powers the
Hanzo Cloud build plane (ghcr.io/hanzoai/pack:latest). It inspects your
repository, detects the language, framework, dependencies, and entry point, and
emits an optimized OCI container image via BuildKit with zero configuration required.
It serves as the canonical builder for kind: fn and zero-Dockerfile builds
in Hanzo Platform, wired directly as the default BuildKit frontend at
k8s.go:880.
Features
- Automatic Ecosystem Detection — Node.js, Next.js, Python, Go, Rust, Ruby, PHP, Java, static HTML, and more.
- BuildKit Gateway Frontend — Runs natively inside BuildKit without requiring Docker daemon access or privileged containers.
- Optimized Layer Caching — Multi-stage builds that cache language runtimes, package managers, and dependencies independently from application source code.
- Deterministic Artifacts — Consistent, reproducible builds across developer machines and in-cluster CI runners.
Quick Start
Standalone CLI
# Build the pack binary
go install github.com/hanzoai/pack/cmd/cli@latest
# Build an application from source
pack build .
BuildKit Dockerfile-less Build
Specify Hanzo Pack as the #syntax gateway in your build:
# Build directly with docker buildx using the pack frontend
docker buildx build \
--build-arg BUILDKIT_SYNTAX=ghcr.io/hanzoai/pack:latest \
-t my-app:latest .
Supported Ecosystems
| Ecosystem | Detected Files | Build / Start Strategy |
|---|---|---|
| Node.js / Bun / Deno | package.json, bun.lock, deno.json |
Detects package manager (npm, pnpm, yarn, bun), installs deps, runs build, starts server |
| Python | pyproject.toml, requirements.txt, Pipfile |
Detects uv, poetry, or pip; builds virtualenv; detects WSGI/ASGI entrypoint |
| Go | go.mod |
Compiles static Linux binary with Go toolchain caching |
| Rust | Cargo.toml |
Cargo build with release profile and sccache support |
| Static Web | index.html |
Ultra-lightweight Nginx / static web server |
Architecture
Hanzo Pack is designed to run in two modes:
- Local CLI (
cmd/cli): Developer CLI communicating with a local BuildKit daemon. - Cluster Gateway Frontend (
ghcr.io/hanzoai/pack): Invoked by Hanzo CI/CD runners (hanzoai/platform) as an in-cluster BuildKit job. When a repo contains no Dockerfile (or declareskind: fn), Hanzo Cloud delegates to Pack to detect and construct the container.
License
MIT License. See LICENSE for details.