Skip to content

docs/usermanuals/en/operations/docker.md: broken example — docker run ... ghcr.io/hodetech/forgelm:latest forgelm --config ..., compose command: forgelm --config ..., and `docker run --gpus all f… (DOC-D3B02-018) #218

Open

Description

@cemililik

Wave 1 · theme D1-10: Documentation-only fixes · highest severity High · 1 finding(s) · effort docs fix

Summary

Every documented docker run fails.

Primary finding

DOC-D3B02-018 — docs/usermanuals/en/operations/docker.md: broken example — docker run ... ghcr.io/hodetech/forgelm:latest forgelm --config ..., compose command: forgelm --config ..., and `docker run --gpus all f…

severity High · already tracked: KNOWN-OPEN C31-DOCKER-RUNBOOK docs/roadmap/phase-16-trust-surface-hardening.md:691-692

Where. docs/usermanuals/en/operations/docker.md:20-21,61,87 (Turkish mirror: docs/usermanuals/tr/operations/docker.md:20-21,61,87) · type: broken example

The document says. docker run ... ghcr.io/hodetech/forgelm:latest forgelm --config ..., compose command: forgelm --config ..., and docker run --gpus all forgelm:custom forgelm --version.

What the code does. The image ENTRYPOINT is ["forgelm"], so these run forgelm forgelm .... argparse rejects that with "invalid choice: 'forgelm'" and exit 2 (reproduced).

Code references. Dockerfile:112

User impact. Every documented docker run fails.

Proposed correction. Drop the leading forgelm: docker run --gpus all ... forgelm:custom --config /workspace/configs/run.yaml and docker run forgelm:custom --version.

Turkish mirror. the Turkish page has the same error; fix both in the same PR

Acceptance criteria

  • Each statement is re-checked against the code at fix time.
  • Documentation listed above is corrected in English and in its Turkish mirror in the same PR.
  • Every finding in this issue is resolved or explicitly closed with a reason.

Found by the October 2026 ForgeLM code and documentation review against commit cab2947. Code links point at that commit; line numbers may have moved since. Finding IDs (CR-…, DOC-…, TECH-…) are stable references for this backlog.

Metadata

Metadata

Assignees

No one assigned

    Labels

    backlog: knownAlready tracked in docs/roadmapblockedWaits for another issue (see Blocked by); set and removed automatically, never by handdocumentationImprovements or additions to documentationseverity: highWrong behaviour or a false claim users rely onsource: review-2026-10Found by the October 2026 code and documentation reviewwave: 1Roadmap wave 1: high severity, small effort

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions