This guide is for managed Codex or CI-style containers where you control a repo checkout and setup script, but do not control the host machine or a long-lived Docker Desktop style environment.

Use this path when:

• the container is ephemeral or cache-backed
• you only have a setup script and optional maintenance script
• hack global install is too heavy or not applicable
• you want env resolution, host exec, agent integrations, and repo-local CLI workflows without the full local host stack

Hack publishes a portable slim image for managed containers:

• Docker Hub: hackdance/hack:slim
• GHCR: ghcr.io/hack-dance/hack:slim

Use it as a base image when you want hack and Bun preinstalled, then layer any project-specific toolchains on top. For example, a non-JS repo can extend the image and add Rust, Go, or other language runtimes without rebuilding the Hack bootstrap each time.

This is the intended baseline for a Codex-style remote environment:

• base image: hackdance/hack:slim
• repo checked out into the working directory
• HACK_ENV_SECRET_KEY injected by the runtime or secret manager
• repo-specific toolchains added on top as needed

Example Dockerfile:

FROM hackdance/hack:slim

RUN apt-get update \
  && apt-get install -y --no-install-recommends \
    build-essential \
    pkg-config \
    python3 \
  && rm -rf /var/lib/apt/lists/*

WORKDIR /workspace

If your repo also needs Rust, Go, or Python packaging tools, add them in this layer rather than waiting for Hack to ship a universal image.

Example setup script:

set -euo pipefail

bun install --frozen-lockfile || bun install

Example maintenance script:

set -euo pipefail

bun install --frozen-lockfile || bun install

Example runtime env injection:

export HACK_ENV_SECRET_KEY="..."

hack env list --json --show-secrets
hack host exec -- printenv DATABASE_URL
hack host exec --scope api -- bun test

CI exercises this contract in scripts/portable-container-smoke.sh: it copies examples/basic into a temp fixture, seeds values with hack env add, removes the local .hack.secret.key, mounts the fixture into the CI-built slim image, injects HACK_ENV_SECRET_KEY, and verifies both hack env list and hack host exec resolve the committed env correctly.

Scripts and agents in containers should also set HACK_NO_INTERACTIVE=1 (or pass --no-interactive): commands then fail fast with E_INTERACTIVE_REQUIRED instead of blocking on a prompt that can never be answered. Set NO_COLOR=1 for log-clean output, and use the --json envelope ({ok, data | error: {code, message}}) on up/down/restart/doctor for CI assertions.

Slim mode is enabled by setting HACK_EXECUTION_MODE=codex or HACK_EXECUTION_MODE=slim.

It is designed to skip machine-level Hack surfaces:

• Caddy
• CoreDNS
• Loki
• Grafana
• local CA and TLS bootstrap
• Docker event watching in hackd

This mode is intentionally not a substitute for a full local workstation setup.

Run this in your managed Codex setup script:

curl -fsSL \
  https://github.com/hack-dance/hack/releases/latest/download/hack-codex-install.sh \
  | bash

The installer resolves the latest release tag, downloads the platform tarball, installs the binary and bundled assets under ~/.hack/ (override with HACK_INSTALL_BIN), and writes a thin hack wrapper with these defaults:

• HACK_EXECUTION_MODE=codex
• HACK_DAEMON_DISABLE_DOCKER_EVENTS=1
• HACK_SETUP_SYNC_MODE=warn
• HACK_ASSETS_DIR pointed at the installed assets

For reproducible CI, pin the release with HACK_INSTALL_TAG or HACK_INSTALL_VERSION (and HACK_RELEASE_BASE_URL for mirrors) instead of tracking latest.

If you are already inside a container built from hackdance/hack:slim, Hack and Bun are already available with the same three mode defaults baked into the image env, and you can skip the installer entirely.

When you are not using the slim image:

set -euo pipefail

mise install "bun@$(awk '/^bun /{print $2}' .tool-versions)"
export PATH="$HOME/.local/share/mise/shims:$PATH"

bun install
curl -fsSL \
  https://github.com/hack-dance/hack/releases/latest/download/hack-codex-install.sh \
  | bash

When you are using the slim image as your base:

set -euo pipefail

bun install --frozen-lockfile || bun install

When you are not using the slim image:

set -euo pipefail

mise install "bun@$(awk '/^bun /{print $2}' .tool-versions)"
export PATH="$HOME/.local/share/mise/shims:$PATH"

bun install --frozen-lockfile || bun install

When you are using the slim image as your base:

set -euo pipefail

bun install --frozen-lockfile || bun install

If you are developing inside the Hack repo itself, the repo-local helpers are still available:

bash scripts/install-codex-slim.sh
bash scripts/maintain-codex-slim.sh

• hack env list
• hack host exec
• hack host shell
• repo-local docs, specs, and agent setup
• command and config surfaces that do not require the machine-wide runtime stack

If the repo uses the modern env overlay model, provide secret decryption material with HACK_ENV_SECRET_KEY instead of relying on a local .hack.secret.key file. (On a developer machine you rarely need this: linked worktrees inherit the key through the git common dir — the env var is for CI, containers, and detached checkouts. See Env & secrets.)

export HACK_ENV_SECRET_KEY="..."
hack host exec --env qa --scope api -- bun db:migrate
hack host exec --env qa --scope api --target compose -- bun test

That same pattern is the recommended portable-container contract:

• mount or check out the repo normally
• inject HACK_ENV_SECRET_KEY from the container runtime or secret manager
• let Hack resolve .hack/hack.env.default.yaml, overlays, and worktree-local overrides at runtime

Do not bake .hack.secret.key into the image.

Portable smoke test:

bun run smoke:portable-container

hack host exec and hack host shell default to a host-local env view for host commands. Use --scope when you want service-scoped values without running inside that service container. Use --target compose when you explicitly want the container-oriented compose view instead. If you are checking a value, prefer hack host exec -- printenv KEY or hack host exec -- sh -lc 'printf "%s\n" "$KEY"'; plain echo $KEY expands in the parent shell before Hack injects env. Use hack host exec --shell 'echo $KEY' if you want Hack to start the child shell after env injection.

The machine-wide hack global surface (install, up, down, status, trust, ca, cert, logs, and logs-reset) is slim-gated, along with explicit Loki-backed log paths such as hack logs --loki.

When you need full remote runtime orchestration instead of repo-local agent workflows, the remote node container image exists — but note that the entire remote/node/gateway/dispatch surface is unsupported experimental in v3 (hidden behind hack help --all), not a supported product path.