You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/technical/detectors/docker_info_detector.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,15 +20,16 @@ Unlike other detectors, Docker Info uses a flattened output structure:
20
20
21
21
```json
22
22
{
23
-
"_container-info": {
23
+
"source": {
24
+
"type": "container",
24
25
"name": "container-name",
25
26
"image": "nginx:latest",
26
27
"hash": "sha256:abc123def456..."
27
28
}
28
29
}
29
30
```
30
31
31
-
This simplified format reflects that container metadata is fundamentally different from package dependencies.
32
+
This simplified format reflects that source metadata is fundamentally different from package dependencies. The `type` field distinguishes between container and host sources.
Docker container info has `container` scope in the orchestrator logic, but outputs directly as `_container-info` to distinguish it from package managers.
90
+
Docker container info has `container` scope in the orchestrator logic, but outputs directly as `source` with `type: "container"` to distinguish it from package managers.
90
91
91
92
### Executor Context
92
93
@@ -122,7 +123,8 @@ The detector returns a tuple: `(packages, metadata)` but is handled specially by
0 commit comments