Pass --time 0 to docker rm -f

[jameshearttech]

• Dev Containers CLI calls docker rm -f with a 15-second timeout
• OCI default stop timeout is 10 seconds
• That leaves only ~5 seconds of margin for process overhead, SSH, WSL2 pipe latency
• On Windows with Podman the overhead consistently consumes that margin, causing intermittent failures
• Fix suggestion: pass --time 0 to docker rm -f since graceful shutdown is irrelevant during a container rebuild

1..3 | ForEach-Object { Measure-Command { podman rm -f $(podman run -d mcr.microsoft.com/devcontainers/base:alpine sleep infinity) } | Select-Object TotalSeconds }
TotalSeconds
------------
       11.73
       11.67
       11.80

1..3 | ForEach-Object { Measure-Command { podman rm -f --time 0 $(podman run -d mcr.microsoft.com/devcontainers/base:alpine sleep infinity) } | Select-Object TotalSeconds }

TotalSeconds
------------
        1.55
        1.58
        1.60

[jameshearttech]

I added --stop-timeout=0 to runArgs in devcontainer.json.

[jameshearttech]

This occurred 14 times for me today while troubleshooting.

Get-ChildItem "$env:APPDATA\Code\logs" -Recurse -Filter "remoteContainers*.log" | Select-String "Stop \(1[0-9]{4} ms\): Run: podman rm -f" | Measure-Object | Select-Object Count

Count
-----
   14

[jameshearttech]

I ended up removing --stop-timeout=0 to runArgs in devcontainer.json because it was causing issues.