# Command Reference Run these commands from the repository root. Run `ct run dev-install-den` first when you want to use direct `den ...` commands from the development environment. ## Rootfs And Workspace | Command | Description | | --- | --- | | `ct run lock` | Lock the conda workspace using the configured Den package channel. | | `ct run install-system` | Install the target image workspace `system` environment. | | `ct run install-runtime` | Install the target image workspace `runtime` environment. | | `ct run workspace-archive` | Create `build/den-workspace.tar.zst`. | | `ct run rootfs` | Stage the Den rootfs under `build/rootfs`. | | `ct run smoke` | Build and validate the staged rootfs userland. | ## Den System Manager | Command | Description | | --- | --- | | `den status` | Show release, generation, channel, boot metadata, and validation status. | | `den doctor` | Check active generation, rootfs layout, metadata, state dirs, and image state. | | `den generations current` | Print the active generation number. | | `den generations list` | List installed generations and mark the active one. | | `den generations validate ` | Validate a generation's prefix, init, and receipt files. | | `den generations diff ` | Compare package inventories for two generations. | | `den update --dry-run` | Print the next generation transaction plan without changing the system. | | `den update --archive ` | Install, record, validate, and activate the next generation from a workspace archive. | | `den activate ` | Validate and activate an installed generation. | | `den rollback [n]` | Roll back to an older or specific generation. | | `den prune --keep ` | Plan inactive generation cleanup; add `--yes` to remove. | | `den channels list` | List channels from `/etc/den/conda.toml`. | | `den channels set ...` | Replace channels in `/etc/den/conda.toml`. | | `den channels release-train` | Print the active Den package release train from forge metadata. | | `den seed status` | Inspect NoCloud seed state. | | `den ssh keys` | List SSH host keys. | | `den boot status` | Inspect stage1, systemd, and boot artifact metadata. | | `den verify rootfs` | Validate the staged rootfs in-toto receipt and tree digest. | | `den verify rootfs-image` | Validate the ext4 rootfs image receipt and image hash. | | `den verify qemu-bundle` | Validate the QEMU bundle receipt, artifact hashes, and receipt inputs. | | `den verify uefi` | Validate the UEFI raw/qcow2 disk receipt and disk hashes. | | `den verify release` | Validate a complete Den release directory and release receipt. | | `den release prepare` | Assemble release files and write the aggregate release receipt. | | `den release download` | Download files declared by an already authenticated release receipt. | | `den sandbox run` | Run a command in a Den sandbox backend and write an execution receipt. | | `den sandbox verify` | Validate a sandbox execution receipt and output tree digest. | | `den sandbox inspect` | Print sandbox defaults and supported backends. | | `den sandbox clean` | Remove sandbox output and work directories. | | `conda den --help` | Access the same command surface through conda's plugin system. | ## Recipes | Command | Description | | --- | --- | | `den forge recipes render` | From `den-forge`, render all Den-owned recipes for `TARGET_PLATFORM`, defaulting to `linux-aarch64`. | | `den forge recipes build` | From `den-forge`, build Den-owned packages into `build/conda`. | | `den forge recipes verify-artifacts` | From `den-forge`, verify `build/conda/den-package-receipt.json` against the current forge inputs and package hashes. | | `den forge recipes write-receipt` | From `den-forge`, write `build/conda/den-package-receipt.json` for the current package artifacts. | | `den forge index` | From `den-forge`, index `build/conda` as a local conda channel. | | `den forge publish-channel` | From `den-forge`, publish one indexed channel subdir to S3-compatible storage. | | `den forge validate` | From `den-forge`, validate `forge/` metadata against `recipes/`. | | `den forge recipes list` | From `den-forge`, list Den-owned recipes in build order. | | `den forge recipes changed --base --head ` | From `den-forge`, list packages changed between git refs, including dependent packages. | ## Buildroot | Command | Description | | --- | --- | | `den image early-boot` | Download Buildroot if needed, apply the Den defconfig, and build the kernel/initramfs. | | `rm -rf build/buildroot-output` | Delete the cached Buildroot output when intentional. | ## Images And Boot | Command | Description | | --- | --- | | `ct run rootfs-image` | Create `build/artifacts/den-rootfs.ext4`. | | `ct run boot-smoke` | Boot QEMU through stage1 and run a bash smoke. | | `ct run boot-systemd-smoke` | Boot QEMU through packaged systemd and run the systemd smoke. | | `ct run generation-smoke` | Create, activate, validate, and roll back a second generation. | | `ct run image-bundle` | Create the target QEMU bundle under `build/artifacts/`. | | `ct run image-bundle-smoke` | Verify the extracted QEMU bundle and boot it. | | `ct run oci-image` | Build the local `den:dev` Docker/OCI inspection image. | | `ct run oci-smoke` | Build `den:dev` and verify basic Den userland inside Docker. | | `ct run uefi-image` | Build the target UEFI raw and qcow2 disk images. | | `ct run uefi-image-smoke` | Boot a seeded UEFI smoke copy with target-specific UEFI firmware in QEMU. | | `ct run virtualbox-image` | Convert the target UEFI raw disk to a VDI image. | | `den image --help` | Inspect image-building commands. | | `den smoke --help` | Inspect smoke-test commands. | | `den smoke rootfs` | Validate a staged rootfs directly. | | `den smoke rootfs --runner chroot` | Validate a staged rootfs through native Linux chroot. | | `den smoke generation` | Validate update and rollback behavior directly. | | `den smoke qemu-bundle --runner native` | Verify and boot a bundle on a native runner. | | `den smoke uefi --runner native` | Build and boot the UEFI smoke disk on a native runner. | ## Safety Normal targets should not: - install host packages, - modify host boot settings, - require privileged host mounts, - require private package-channel credentials.