docs: the published tags were still 0.2.21

The full image is 0.2.81 and its real size is ~25 GB on disk / ~14 GB
pulled, not ~28 GB. Also say that capability images version independently
and name the nine still sitting at 0.2.18.
Co-Authored-By: 's avatarClaude Opus 5 <noreply@anthropic.com>
parent 5a86dc67
......@@ -7,7 +7,7 @@ public, pulled without credentials. There is nothing to build.
| Package | What it is | Pull |
|---|---|---|
| `ghcr.io/nextime/coderai` | **The full CoderAI** — every capability, every engine, the Web Studio and admin UI, the cluster head/node, llama.cpp with the RPC backend and `rpc-server`. One layer, ~28 GB. Tags: `latest`, `0.2.21`, … | `docker pull ghcr.io/nextime/coderai:latest` |
| `ghcr.io/nextime/coderai` | **The full CoderAI** — every capability, every engine, the Web Studio and admin UI, the cluster head/node, llama.cpp with the RPC backend and `rpc-server`. One layer, ~25 GB on disk (≈14 GB to pull). Tags: `latest`, `0.2.81`, … | `docker pull ghcr.io/nextime/coderai:latest` |
| `ghcr.io/nextime/coderai-images` | Image generation only (SDXL, Flux, Z-Image …) | `docker pull ghcr.io/nextime/coderai-images:latest` |
| `ghcr.io/nextime/coderai-video` | Video generation (Wan, LTX-2 …), upscale, interpolation | `…/coderai-video:latest` |
| `ghcr.io/nextime/coderai-text` | LLMs with transformers / llama.cpp, incl. local LoRA adapters | `…/coderai-text:latest` |
......@@ -34,9 +34,18 @@ cluster node that only needs one thing runs; the full image is what a
workstation runs. All of them expose the same API on port 8000 (capability
images) or 8776 (full image), and all of them can be a cluster node.
Every tag is also published with its version (`:0.2.21`); `:latest` moves
Every tag is also published with its version (`:0.2.81`); `:latest` moves
only after the image has completed a real request on real hardware.
The capability images do not all move together: a profile is rebuilt when its
own dependencies change, so `:latest` is the newest build *of that profile*,
not of the release. At the time of writing the full image and most capability
images are `0.2.81`/`0.2.80`, while `coderai-llama`, `coderai-vllm`,
`coderai-engines`, `coderai-engines-kt`, `coderai-ocr-paddle`,
`coderai-speaker`, `coderai-stt-crisper`, `coderai-stt-nemo` and
`coderai-tts-xtts` are still `0.2.18`. Pull `:latest` and check the version
the image reports on `/healthz` if it matters to you.
**Every published image is signed** with [cosign](https://github.com/sigstore/cosign)
against the key pair in `packaging/cosign.pub` (the private half never
leaves the release machine). Check before you run:
......@@ -54,7 +63,7 @@ a `policy-controller` / `cosign` admission rule on a cluster, or simply the
command above in whatever pulls.
For an offline machine, pull the image where there is a connection and
move it: `docker save ghcr.io/nextime/coderai:0.2.21 | gzip > coderai.tar.gz`
move it: `docker save ghcr.io/nextime/coderai:0.2.81 | gzip > coderai.tar.gz`
there, `docker load < coderai.tar.gz` here.
## Linux
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment