ashlar docker build, ashlar docker run and ashlar docker clean fail with an unhandled MissingMethodException and a stack trace.
A MissingMethodException at runtime points at an assembly/reference mismatch rather than a logic error — the compiled call target is not present in the assembly actually loaded at run time. Worth checking whether these paths are exercised by any test at all; a whole command group failing this way suggests they are not.
Separately, DockerCommand.cs:441 does Environment.ExitCode = result.ExitCode, which is discarded (see the exit-code issue), so ashlar docker run could not propagate a container's exit code even once the crash is fixed.
Found by the round-3 CLI hunt lane bb-cli-contract (78 probes).
ashlar docker build,ashlar docker runandashlar docker cleanfail with an unhandledMissingMethodExceptionand a stack trace.A
MissingMethodExceptionat runtime points at an assembly/reference mismatch rather than a logic error — the compiled call target is not present in the assembly actually loaded at run time. Worth checking whether these paths are exercised by any test at all; a whole command group failing this way suggests they are not.Separately,
DockerCommand.cs:441doesEnvironment.ExitCode = result.ExitCode, which is discarded (see the exit-code issue), soashlar docker runcould not propagate a container's exit code even once the crash is fixed.Found by the round-3 CLI hunt lane
bb-cli-contract(78 probes).