Skip to content

Commit 13d5def

Browse files
Karlclaude
andcommitted
Clarify container_backend auto-detect prefers docker over podman
Existing detectContainerBackend() already does this (checks dockerAvailable() first), but the plan comment didn't say so explicitly. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1 parent 6794c20 commit 13d5def

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/dev/plans/config-revamp.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ os: linux
4646
# Preferred Linux container backend. Valid values: docker, podman, or "" (auto-detect).
4747
# Both work on Linux and macOS. Ignored for vm/vm-enhanced (uses containerd)
4848
# and os=mac (uses Seatbelt or Tart). CLI --backend overrides.
49-
# Empty string (default): auto-detect by checking which binary is available.
49+
# Empty string (default): auto-detect — prefers docker over podman if both are present.
5050
container_backend: ""
5151

5252
# Isolation level for the sandbox.
@@ -126,7 +126,7 @@ Also add a `GenerateScaffoldConfig` function that produces the user-facing scaff
126126
commenting out all uncommented, non-blank lines. The `container_backend` default in the
127127
baked-in YAML is `""` (empty string = auto-detect via `detectContainerBackend()`), matching
128128
existing behavior — this is NOT changing to `"docker"` as that would silently break
129-
Podman-only users on upgrade.
129+
Podman-only users on upgrade. Auto-detect prefers docker over podman if both are present.
130130

131131
```go
132132
// GenerateScaffoldConfig takes the baked-in defaults YAML and returns a version

0 commit comments

Comments
 (0)