@@ -1,14 +1,14 @@
1−# nix-container
1+# container-nix
22
33A Nix flake that builds an **OCI image** (via
44[`nix2container`](https://github.com/nlewo/nix2container)) for running with
55Apple's [`container`](https://github.com/apple/container) CLI on macOS.
66
77It's a plain, single-process image — no NixOS, no systemd — defined in
8−[`flake.nix`](./flake.nix). `c start` drops you into a
9−[`herdr`](https://herdr.dev) session whose panes use your host login shell
10−(detected and bundled by `c init`). You choose what else it ships via a
11−per-project `container.nix`.
8+[`flake.nix`](./flake.nix). The default command is `fish` (with a configured
9+prompt), and the image ships a handful of dev/LLM tools: `git`, `jujutsu`,
10+`ripgrep`, `fd`, `jq`, `nodejs`, `python3`, a Rust + C toolchain,
11+`charmbracelet.crush`, `openssh`, and more.
1212
1313## Prerequisites
1414
@@ -16,102 +16,85 @@ per-project `container.nix`.
1616- Apple's [`container`](https://github.com/apple/container) CLI installed, with
1717 services started: `container system start` (first run downloads a Linux
1818 kernel).
19−- A **Linux builder** *only if you use packages that aren't in the binary
20− cache*. The image is assembled entirely on macOS — the root filesystem is just
21− a host-built symlink tree over the **substituted** Linux store paths — so a
22− fully-cached package set needs no builder. Compiling a Linux package that
23− `cache.nixos.org` doesn't have does, though: use a [remote builder][builders]
24− or, on Apple Silicon, the `nix-darwin` `linux-builder`.
19+- A **Linux builder** — the image *contents* are Linux binaries, which can't be
20+ built on macOS. Use a [remote builder][builders] or, on Apple Silicon, the
21+ `nix-darwin` `linux-builder`. With one configured, `nix` dispatches Linux
22+ builds to it automatically (most packages also come prebuilt from the binary
23+ cache, so the builder is only needed for the uncached bits).
2524
2625[builders]: https://nix.dev/manual/nix/latest/advanced-topics/distributed-builds
2726
28−## Packages
29−
30−`init` builds the image from a **`container.nix`** in the current directory — an
31−attrset with a `packages` function (`{ pkgs, nur }` returning the package list;
32−`nur` is [NUR](https://github.com/nix-community/NUR), for packages outside
33−nixpkgs) and an optional `mounts` list. It is **required**; there is no default.
34−
35−```nix
36−# ./container.nix
37−{
38− packages = { pkgs, nur }: with pkgs; [
39− git
40− go
41− nur.repos.charmbracelet.crush
42− ];
43− # Extra "host:container" bind mounts, on top of $PWD → /workspace. A leading
44− # ~/ in the host path expands to $HOME. Optional.
45− mounts = [
46− "~/data:/data"
47− ];
48−}
49−```
27+## Steps
5028
51−Your **host login shell** (detected by `c init`, bash fallback), **coreutils**,
52−[**herdr**](https://herdr.dev) (the session `c start` launches), **Nix** itself
53−(with CA certs and `nix-command`/`flakes` enabled, single-user), and the ncurses
54−**terminfo** database are always included — no need to list them.
29+### 1. Build the image archive
5530
56−Point at a different file with `-c`/`--config`:
31+`nix run` builds the Linux contents (on your Linux builder) and writes a tagged
32+OCI archive locally via `skopeo`. Pass the output path; the image is tagged
33+`nix-container:latest`.
5734
5835```sh
59−nix run github:ilyakooo0/nix-container -- init --config envs/ci.nix
36+nix run . -- image.tar.gz
6037```
6138
62−## Quick start
63−
64−No clone needed — `nix run` drives everything. Run it from a project directory
65−that holds a `container.nix`; the container is named after that directory.
39+### 2. Load it into `container`
6640
6741```sh
68−# build the image, load it, and create the container (named after $PWD):
69−nix run github:ilyakooo0/nix-container -- init
42+container image load --input image.tar.gz
43+```
7044
71−# start it and attach — drops you into a herdr session:
72−nix run github:ilyakooo0/nix-container -- start
45+### 3. Create and start the container
46+
47+```sh
48+container create --name nixos --ssh -it nix-container:latest
49+container start -ai nixos
7350```
7451
75−- `init` builds the OCI archive in a temp dir, loads it into `container`,
76− deletes the temp file, then (re)creates the container. It mounts the current
77− directory at `/workspace` (the container's working directory).
7852- `--ssh` forwards your host SSH agent socket into the container (so `git` over
79− SSH works with your keys).
80−- Add more mounts persistently via `mounts` in `container.nix` (above), or
81− ad-hoc by passing them through to `create` (mounts can only be set at creation):
53+ SSH etc. works with your keys).
54+- `-it` / `-ai` give an interactive TTY; `start -ai` attaches to it.
8255
83− ```sh
84− nix run github:ilyakooo0/nix-container -- init -v $HOME/data:/data
85− ```
56+You land in `fish`. Exit the shell to stop the container.
8657
87−Working from a checkout, [`./c init`](./c) / `./c start` are equivalent — and
88−`c` can be symlinked onto your `$PATH` and run from any project.
58+> **Shortcut:** the [`c`](./c) script wraps create/start and names the container
59+> after the current directory (handy for per-project containers):
60+>
61+> ```sh
62+> ./c init # create; append create args to add mounts, e.g.
63+> ./c init -v $PWD:/work # (mounts can only be set at creation time)
64+> ./c start # start and attach
65+> ```
8966
9067## Re-running after a rebuild
9168
92−Just run `init` again — it reloads the image and replaces the existing container
93−(removing the old one first), so there's nothing to clean up:
69+`container` keeps the loaded image and the created container, so to pick up a
70+new build, remove the old ones first:
9471
9572```sh
96−nix run github:ilyakooo0/nix-container -- init
73+nix run . -- image.tar.gz # rebuild the archive
74+container rm nixos # remove the old container (stop it first if running)
75+container image rm nix-container:latest
76+container image load --input image.tar.gz
77+container create --name nixos --ssh -it nix-container:latest
78+container start -ai nixos
9779```
9880
99−## Customize further
81+## Other image destinations
82+
83+`nix run .#copyTo` is nix2container's generic skopeo wrapper
84+(`skopeo copy nix:<image> "$@"`) — the argument is any skopeo destination:
85+
86+```sh
87+nix run .#copyTo -- docker://ghcr.io/me/nixos:latest # push to a registry
88+nix run .#copyTo -- docker-daemon:nix-container:latest # local Docker daemon
89+```
10090
101−Fork or clone to change what isn't per-project — `config.cmd`/`env` or the image
102−name — in [`flake.nix`](./flake.nix). The flake also exposes build helpers:
91+## Customize
10392
104−- `lib.<system>.copyWith` → a skopeo copy app for a `{ pkgs, nur }: [ ... ]`
105− function, for building/pushing the image anywhere skopeo can write (e.g. a
106− registry):
93+Edit the `buildImage` call in [`flake.nix`](./flake.nix):
10794
108− ```sh
109− drv=$(nix build --no-link --print-out-paths --impure --expr \
110− '(builtins.getFlake "github:ilyakooo0/nix-container").lib.${builtins.currentSystem}.copyWith (import ./container.nix).packages')
111− $drv/bin/copy-to docker://ghcr.io/me/img:latest
112− ```
113−- `lib.<system>.mkImage <name> <shell>` → the underlying OCI image (`copyWith`
114− defaults these to `nix-container` / `bash`).
95+- Add packages to `copyToRoot.paths`.
96+- Change the default process via `config.cmd`.
97+- Add env vars via `config.env`.
11598
11699The flake uses `flake-utils` over `{aarch64,x86_64}-{darwin,linux}`; the host
117100system maps to the matching Linux target automatically (an Intel Mac builds an
@@ -119,12 +102,9 @@ system maps to the matching Linux target automatically (an Intel Mac builds an
119102
120103## How it works
121104
122−- **Contents** are Linux store paths — downloaded prebuilt from the binary cache
123− (only built on a Linux builder if not cached).
124−- **Assembly** runs entirely on your Mac: `copyToRoot` is a *host-arch* `buildEnv`
125− symlink tree over those Linux paths (symlinks are arch-neutral), and
126− `nix2container` + `skopeo` package it — so for a cached set, `init` produces a
127− loadable Linux image with no Linux build at all.
105+- **Contents** (`copyToRoot`) are built from `pkgsLinux` → the Linux builder.
106+- **Assembly** (`nix2container` + the `skopeo` copy) runs on your Mac, so a
107+ single `nix run` produces a loadable archive.
128108- Apple's `container` runs each container in its own lightweight Linux VM and
129109 consumes standard OCI images — no `--privileged` or systemd needed.
130110