Move container registry to docker.dcglab.co.uk/kb
registry.dcglab.co.uk has been decommissioned and replaced by docker.dcglab.co.uk. Images move off the Gitea built-in registry (which never successfully accepted a push) to the new host, published at the root with no org segment: docker.dcglab.co.uk/kb/engine and .../kb/mcp. IMAGE_ORG is now empty by default but still honoured when set, so the documented REGISTRY=ghcr.io IMAGE_ORG=myorg override keeps working. Gitea remains the git forge — the release download URLs in README.md are unchanged and still point at gitea.dcglab.co.uk. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -65,7 +65,7 @@ The project SHALL provide Docker Compose files for single-command deployment. Co
|
||||
|
||||
#### Scenario: Pre-built image deployment
|
||||
- **WHEN** an admin wants to use a pre-built engine image without building from source
|
||||
- **THEN** the engine release notes SHALL include the exact `docker pull` command with the versioned tag (e.g. `gitea.dcglab.co.uk/steve/kb/engine:engine-v2.1.0-nvidia`)
|
||||
- **THEN** the engine release notes SHALL include the exact `docker pull` command with the versioned tag (e.g. `docker.dcglab.co.uk/kb/engine:engine-v2.1.0-nvidia`)
|
||||
|
||||
#### Scenario: MCP allowed hosts in Compose
|
||||
- **WHEN** the kb-mcp service is defined in a Compose file
|
||||
|
||||
Reference in New Issue
Block a user