#4316 [Docs] DOCKER.md: name the old-daemon start that looks like a card or image problem

closed · @XiaoBinGan · 0 Kommentare · Auf GitHub

NVIDIA / CUDASecurityDocumentation

Beschreibung

## Problem and result

A host whose Docker predates 20.10 starts the image and gets:

```text
[X] The engine in this image does not match this computer's graphics card, or the card is not visible to the container.
    strata: no usable Python found.
```

The card, the driver, the toolkit and the image flavour are all fine. That daemon's default seccomp profile
denies `access(X_OK)`, so the launcher's "is this Python executable?" test answers no for the bundled
runtime — which is present and runs. `docs/DOCKER.md` already has a troubleshooting entry that begins with
exactly that first sentence and sends the reader to the card, the toolkit and the image flavour, so a reader
with this cause is sent the wrong way and nothing in the document mentions `seccomp`.

After this change the section names the case, gives three commands that tell the two apart inside the image
(nothing is downloaded), says what the combination means, and gives the one-option fix with its compose
spelling.

## Related discussion

#4309 (the report) and #4312 (the launcher and the entrypoint no longer depend on that
test). Those are code; this is the document a reader on a released image reaches, where the bug is still
present.

## Approach

One entry in `Troubleshooting`, placed directly after the card-mismatch entry so the two are read together.
It does not restate the existing entry and does not change any other section.

## Validation

**Passed:** the three commands exactly as written, against the image the document names
(`ghcr.nju.edu.cn/niko1221/strata:0.2.2-cuda13`, mirror of `ghcr.io`), on the host that shows the bug
(Docker 19.03.15, default seccomp):

```text
1) denied
2) present
3) Python 3.12.15
```

**Passed:** the documented fix, the same container with `--security-opt seccomp=unconfined`, prints
`strata 0.2.2 (build 0.1.47; python 3.12.15 at /opt/strata/terminal/python/bin/python3)`. Without the option
the same command prints the two lines quoted above.

**Passed:** the file keeps the document's style (bold symptom first, then cause, then a command block) and its
Markdown: the new block is inside `## Troubleshooting`, uses fences that match the neighbouring entries, and
the file's line endings stay LF, as the repository stores it.

**Failed:** none.

**Not run:** `docs/DOCKER.md`'s own checks: the repository has no link checker I could run locally for this
page. The entry adds no link, only inline commands and one issue/PR reference that both exist. I did not
build an image or run the compose file, because the change is prose only.

## Limits

- This documents the symptom, not a code change: an image that still carries the old launcher keeps needing
  the option until it is built from #4312.
- The three commands pin the image name in the prose (`IMAGE`) rather than repeating a version, so they stay
  valid for any image; the measured version is named in the text.

Mehr auf der Site

Links zu Install, Modellen, Releases.